sync_mapping_buffers(9) [centos man page]

SYNC_MAPPING_BUFFERS(9) 					   The Linux VFS					   SYNC_MAPPING_BUFFERS(9)

NAME

       sync_mapping_buffers - write out & wait upon a mapping's "associated" buffers

SYNOPSIS

       int sync_mapping_buffers(struct address_space * mapping);

ARGUMENTS

       mapping
	   the mapping which wants those buffers written

DESCRIPTION

       Starts I/O against the buffers at mapping->private_list, and waits upon that I/O.

       Basically, this is a convenience function for fsync.  mapping is a file or directory which needs those buffers to be written for a
       successful fsync.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   SYNC_MAPPING_BUFFERS(9)

USB_BUFFER_MAP_SG(9)						   USB Core APIs					      USB_BUFFER_MAP_SG(9)

NAME

       usb_buffer_map_sg - create scatterlist DMA mapping(s) for an endpoint

SYNOPSIS

       int usb_buffer_map_sg(const struct usb_device * dev, int is_in, struct scatterlist * sg, int nents);

ARGUMENTS

       dev
	   device to which the scatterlist will be mapped

       is_in
	   mapping transfer direction

       sg
	   the scatterlist to map

       nents
	   the number of entries in the scatterlist

DESCRIPTION

       Return value is either < 0 (indicating no buffers could be mapped), or the number of DMA mapping array entries in the scatterlist.

       The caller is responsible for placing the resulting DMA addresses from the scatterlist into URB transfer buffer pointers, and for setting
       the URB_NO_TRANSFER_DMA_MAP transfer flag in each of those URBs.

       Top I/O rates come from queuing URBs, instead of waiting for each one to complete before starting the next I/O. This is particularly easy
       to do with scatterlists. Just allocate and submit one URB for each DMA mapping entry returned, stopping on the first error or when all
       succeed. Better yet, use the usb_sg_*() calls, which do that (and more) for you.

       This call would normally be used when translating scatterlist requests, rather than usb_buffer_map, since on some hardware (with IOMMUs) it
       may be able to coalesce mappings for improved I/O efficiency.

       Reverse the effect of this call with usb_buffer_unmap_sg.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010						      USB_BUFFER_MAP_SG(9)