Main index | Section 9 | Options |
#include <sys/bio.h>
#include <geom/geom.h>
bio_cmd | |
I/O request command. There are five I/O requests available in GEOM: | |
BIO_READ | A read request. |
BIO_WRITE | A write request. |
BIO_DELETE | Indicates that a certain range of data is no longer used and that it can be erased or freed as the underlying technology supports. Technologies like flash adaptation layers can arrange to erase the relevant blocks before they will become reassigned and cryptographic devices may want to fill random bits into the range to reduce the amount of data available for attack. |
BIO_GETATTR | |
Inspect and manipulate out-of-band attributes on a particular provider or path. Attributes are named by ascii strings and are stored in the bio_attribute field. | |
BIO_FLUSH | Tells underlying providers to flush their write caches. |
bio_flags | |
Available flags: | |
BIO_ERROR | |
Request failed (error value is stored in bio_error field). | |
BIO_DONE | Request finished. |
bio_cflags | |
Private use by the consumer. | |
bio_pflags | |
Private use by the provider. | |
bio_offset | |
Offset into provider. | |
bio_data | |
Pointer to data buffer. | |
bio_error | |
Error value when BIO_ERROR is set. | |
bio_done | |
Pointer to function which will be called when the request is finished. | |
bio_driver1 | |
Private use by the provider. | |
bio_driver2 | |
Private use by the provider. | |
bio_caller1 | |
Private use by the consumer. | |
bio_caller2 | |
Private use by the consumer. | |
bio_attribute | |
Attribute string for BIO_GETATTR request. | |
bio_from | |
Consumer to use for request (attached to provider stored in bio_to field) (typically read-only for a class). | |
bio_to | |
Destination provider (typically read-only for a class). | |
bio_length | |
Request length in bytes. | |
bio_completed | |
Number of bytes completed, but they may not be completed from the front of the request. | |
bio_children | |
Number of bio clones (typically read-only for a class). | |
bio_inbed | |
Number of finished bio clones. | |
bio_parent | |
Pointer to parent bio. | |
The g_new_bio() function allocates a new, empty bio structure.
g_alloc_bio() - same as g_new_bio(), but always succeeds (allocates bio with the M_WAITOK malloc flag).
The g_clone_bio() function allocates a new bio structure and copies the following fields from the bio given as an argument to clone: bio_cmd, bio_length, bio_offset, bio_data, bio_attribute. The field bio_parent in the clone points to the passed bio and the field bio_children in the passed bio is incremented.
This function should be used for every request which enters through the provider of a particular geom and needs to be scheduled down. Proper order is:
g_duplicate_bio() - same as g_clone_bio(), but always succeeds (allocates bio with the M_WAITOK malloc flag).
The g_destroy_bio() function deallocates and destroys the given bio structure.
The g_print_bio() function prints information about the given bio structure (for debugging purposes).
The g_reset_bio() function resets the given bio structure back to its initial state. g_reset_bio() preserves internal data structures, while setting all user visible fields to their initial values. When reusing a bio obtained from g_new_bio(), g_alloc_bio(), g_clone_bio(), or g_duplicate_bio() for multiple transactions, g_reset_bio() must be called between the transactions in lieu of bzero(). While not strictly required for a bio structure created by other means, g_reset_bio() should be used to initialize it and between transactions.
void example_start(struct bio *bp) { struct example_softc *sc; struct bio *cbp;printf("Request received: "); g_print_bio(bp); printf(" );
sc = bp->bio_to->geom->softc; if (sc == NULL) { g_io_deliver(bp, ENXIO); return; }
/* Let's clone our bio request. */ cbp = g_clone_bio(bp); if (cbp == NULL) { g_io_deliver(bp, ENOMEM); return; } cbp->bio_done = g_std_done; /* Standard 'done' function. */
/* Ok, schedule it down. */ /* * The consumer can be obtained from * LIST_FIRST(&bp->bio_to->geom->consumer) as well, * if there is only one in our geom. */ g_io_request(cbp, sc->ex_consumer); }
G_BIO (9) | Mar 7, 2018 |
Main index | Section 9 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
“ | … one of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs. | ” |
— Robert Firth |