mirror of
https://github.com/freebsd/freebsd-src
synced 2024-09-06 17:18:32 +00:00
Fix typos.
Approved by: phk
This commit is contained in:
parent
2e2ed5f6e2
commit
c90be48012
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=64891
|
@ -279,7 +279,7 @@ semantics.
|
|||
.PP
|
||||
One particular change which has been proposed is to drop the present
|
||||
requirement that a struct buf be mapped contiguously into kernel
|
||||
address space. The argument goes that since many modern drivers us
|
||||
address space. The argument goes that since many modern drivers use
|
||||
physical address DMA to transfer the data maintaining such a mapping
|
||||
is needless overhead.
|
||||
.PP
|
||||
|
@ -288,7 +288,7 @@ buffer in kernel address space and some kind of compatibility
|
|||
must be provided there.
|
||||
.PP
|
||||
The question is, if such a change is made impossible by the
|
||||
separation of the I/O aspect into its own data structure ?
|
||||
separation of the I/O aspect into its own data structure?
|
||||
.PP
|
||||
The answer to this is ``no''.
|
||||
Anything that could be added to or done with
|
||||
|
@ -355,7 +355,7 @@ struct bio {
|
|||
u_int bio_flags; /* BIO_ flags. */
|
||||
struct buf *_bio_buf; /* Parent buffer. */
|
||||
int bio_error; /* Errno for BIO_ERROR. */
|
||||
long bio_resid; /* Remaining I/0 in bytes. */
|
||||
long bio_resid; /* Remaining I/O in bytes. */
|
||||
void (*bio_done) __P((struct buf *));
|
||||
void *bio_driver1; /* Private use by the callee. */
|
||||
void *bio_driver2; /* Private use by the callee. */
|
||||
|
|
Loading…
Reference in a new issue