mirror of https://gitee.com/openkylin/linux.git
pipe: remove KM_USER0 from comments
Signed-off-by: Cong Wang <amwang@redhat.com>
This commit is contained in:
parent
a8e5202d09
commit
2164d33446
|
@ -224,7 +224,7 @@ static void anon_pipe_buf_release(struct pipe_inode_info *pipe,
|
|||
* and the caller has to be careful not to fault before calling
|
||||
* the unmap function.
|
||||
*
|
||||
* Note that this function occupies KM_USER0 if @atomic != 0.
|
||||
* Note that this function calls kmap_atomic() if @atomic != 0.
|
||||
*/
|
||||
void *generic_pipe_buf_map(struct pipe_inode_info *pipe,
|
||||
struct pipe_buffer *buf, int atomic)
|
||||
|
|
|
@ -86,11 +86,9 @@ struct pipe_buf_operations {
|
|||
* mapping or not. The atomic map is faster, however you can't take
|
||||
* page faults before calling ->unmap() again. So if you need to eg
|
||||
* access user data through copy_to/from_user(), then you must get
|
||||
* a non-atomic map. ->map() uses the KM_USER0 atomic slot for
|
||||
* atomic maps, so you can't map more than one pipe_buffer at once
|
||||
* and you have to be careful if mapping another page as source
|
||||
* or destination for a copy (IOW, it has to use something else
|
||||
* than KM_USER0).
|
||||
* a non-atomic map. ->map() uses the kmap_atomic slot for
|
||||
* atomic maps, you have to be careful if mapping another page as
|
||||
* source or destination for a copy.
|
||||
*/
|
||||
void * (*map)(struct pipe_inode_info *, struct pipe_buffer *, int);
|
||||
|
||||
|
|
Loading…
Reference in New Issue