diff options
author | Cong Wang <amwang@redhat.com> | 2012-06-23 11:33:51 +0800 |
---|---|---|
committer | Cong Wang <amwang@redhat.com> | 2012-07-24 15:27:34 +0800 |
commit | 2164d3344693d2d4799fe91836d61f55516cbdf0 (patch) | |
tree | 842b96f9d534c78bea6c41243adc49fa528911de /include/linux/pipe_fs_i.h | |
parent | a8e5202d09c1bac5b83889e1ddeff146eb421565 (diff) |
pipe: remove KM_USER0 from comments
Signed-off-by: Cong Wang <amwang@redhat.com>
Diffstat (limited to 'include/linux/pipe_fs_i.h')
-rw-r--r-- | include/linux/pipe_fs_i.h | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/include/linux/pipe_fs_i.h b/include/linux/pipe_fs_i.h index e1ac1ce16fb..e11d1c0fc60 100644 --- a/include/linux/pipe_fs_i.h +++ b/include/linux/pipe_fs_i.h @@ -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); |