LWN: Comments on "Driver porting: Zero-copy user-space access"

Driver porting: Zero-copy user-space access

Ajaxelitus — Wed, 08 May 2013 21:37:13 +0000

Another, much more modern and very tiny example may be found at

https://gist.github.com/17twenty/2930467

Driver porting: Zero-copy user-space access

will — Fri, 13 Mar 2009 18:26:12 +0000

> For a good example of how to use get_user_pages() in a char driver, see the definition of sgl_map_user_pages() in drivers/scsi/st.c.

Driver porting: Zero-copy user-space access

bmasood — Thu, 18 Dec 2008 06:37:17 +0000

Bart,

I am facing the exact problem that you mentioned: Need to get my data from device to user space as efficiently as possible. I was wondering if you did find any example?

Thanks
Bilal

Driver porting: Zero-copy user-space access

dnevil — Thu, 06 Sep 2007 16:31:02 +0000

Try booting with a kernel parameter of "highmem=0".

Driver porting: Zero-copy user-space access

dnevil — Thu, 06 Sep 2007 15:28:13 +0000

Sounds like your system is allocating memory from ZONE_HIGHMEM (since you are on a heavily loaded system, and you are probably running i386). The comments in include/linux/mm_types states that if page->virtual is null then the page is not mapped into kernel virtual memory (i.e. it is HIGHMEM). You should try allocating your memory as soon after system boot as possible. Are there other 'tricks' for assuring that user-allocated memory comes from ZONE_NORMAL or ZONE_DMA?

Driver porting: Zero-copy user-space access

bartjes — Fri, 20 Jul 2007 12:43:48 +0000

As I am quite new with Linux, searching the entire morning to find a solution for getting data out of my driver to a user application as efficient as possible, I stumble accross deprecanted mechanisms, function prototypes, and sometimes even a bit of explanation.
All this looks very complex to me and I REALLY could use a basic example where a piece of shared memory is allocated, freed, passed from driver to user-spacve or vice versa, and how the driver fills information into the structure and how the user process can read this.

It's sad that while searching all morning, an example is nowhere to be found, or it's way too complicated to understand, does compile with my terminal full of errors.....

Any suggestion would be helpful, Thanks, Bart

Driver porting: Zero-copy user-space access

yltian — Sat, 02 Jun 2007 01:48:11 +0000

Please "grep get_user_pages linux/drivers/media/video/video-buf.c". It's a good example. V4L2 uses this method to share memory betweent DMA and application.

Driver porting: Zero-copy user-space access

ceb — Wed, 15 Feb 2006 17:17:47 +0000

Does anyone have any experience in using get_user_pages in a real system. As far as I can tell it is totally unreliable when the machine is in any way loaded. As well as getting zero addresses for pages returned, the physical addresses don't seem to correspond to the data to be transferred. This is on various flavors of Linux 2.6 based kernels.

This seems to rule out performing DMA directly from user space but I would like to be told that I'm wrong.

Driver porting: Zero-copy user-space access

rwbowman — Wed, 02 Nov 2005 21:29:42 +0000

TRUE or FALSE - if I map and lock a user space buffer using get_user_pages during ioctl, and then allow the ioctl to return, the pages will remnain locked until I release them with page_cache_release.

I've heard (twice now) where folks say they don't remain locked.?
Thanks!

Driver porting: Zero-copy user-space access

bhepple — Wed, 03 Mar 2004 07:55:24 +0000

Hmmm, a quick recursive grep through the 2.6.3 driver source and include files showed exactly 0 users of set_page_dirty_lock() and 1 user of put_page() (in drivers/char/agp/generic.c)

There _is_ a
#define page_cache_release(page) put_page(page)
in include/linux/pagemap.h and it is quite a popular little chap in the device driver code with 13 hits in the entire tree.

Am I missing something or should we be using page_cache_release instead of put_page and is it (and set_page_dirty_lock) _really_ needed after all - I can hardly believe all those drivers are causing "data corruption and grumpy users"...

Driver porting: Zero-copy user-space access

grisu1976 — Fri, 13 Feb 2004 14:34:34 +0000

I don't really understand why the kiobuf interface does not exist anymore. In linux kernel 2.4 the kiobuf interface used get_user_pages, or am i wrong? The kiobuf interface was easier to use than get_user_pages - that's my opinion