bio_copy_user(9) [centos man page]

BIO_COPY_USER(9)						   The Linux VFS						  BIO_COPY_USER(9)

NAME

       bio_copy_user - copy user data to bio

SYNOPSIS

       struct bio * bio_copy_user(struct request_queue * q, struct rq_map_data * map_data, unsigned long uaddr, unsigned int len, int write_to_vm,
				  gfp_t gfp_mask);

ARGUMENTS

       q
	   destination block queue

       map_data
	   pointer to the rq_map_data holding pages (if necessary)

       uaddr
	   start of user address

       len
	   length in bytes

       write_to_vm
	   bool indicating writing to pages or not

       gfp_mask
	   memory allocation flags

DESCRIPTION

       Prepares and returns a bio for indirect user io, bouncing data to/from kernel pages as necessary. Must be paired with call bio_uncopy_user
       on io completion.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							  BIO_COPY_USER(9)

BLK_MAKE_REQUEST(9)						   Block Devices					       BLK_MAKE_REQUEST(9)

NAME

       blk_make_request - given a bio, allocate a corresponding struct request.

SYNOPSIS

       struct request * blk_make_request(struct request_queue * q, struct bio * bio, gfp_t gfp_mask);

ARGUMENTS

       q
	   target request queue

       bio
	   The bio describing the memory mappings that will be submitted for IO. It may be a chained-bio properly constructed by block/bio layer.

       gfp_mask
	   gfp flags to be used for memory allocation

DESCRIPTION

       blk_make_request is the parallel of generic_make_request for BLOCK_PC type commands. Where the struct request needs to be farther
       initialized by the caller. It is passed a struct bio, which describes the memory info of the I/O transfer.

       The caller of blk_make_request must make sure that bi_io_vec are set to describe the memory buffers. That bio_data_dir will return the
       needed direction of the request. (And all bio's in the passed bio-chain are properly set accordingly)

       If called under none-sleepable conditions, mapped bio buffers must not need bouncing, by calling the appropriate masked or flagged
       allocator, suitable for the target device. Otherwise the call to blk_queue_bounce will BUG.

WARNING

       When allocating/cloning a bio-chain, careful consideration should be given to how you allocate bios. In particular, you cannot use
       __GFP_WAIT for anything but the first bio in the chain. Otherwise you risk waiting for IO completion of a bio that hasn't been submitted
       yet, thus resulting in a deadlock. Alternatively bios should be allocated using bio_kmalloc instead of bio_alloc, as that avoids the
       mempool deadlock. If possible a big IO should be split into smaller parts when allocation fails. Partial allocation should not be an error,
       or you risk a live-lock.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010						       BLK_MAKE_REQUEST(9)