Hi, On Thu, Sep 12, 2002 at 09:24:56AM -0600, Joseph A. Knapka wrote: > > I just read about the kiobuf interface in the Linux Device Driver book from Rubini/Corbet, and there is one point, which I don't understand: > > - map_user_kiobuf() forces the pages within a user space address range into physical memory, and increments their usage count, which subsequently prevents the pages from > > being swapped out. > > While it's true that having a non-zero reference count will prevent > a page from being swapped out, such a page is still subject to > all normal VM operations. In particular, the VM might unmap > the page from your process, *decrement its reference count*, and > then swap it out. No. The VM may unmap the page, and it may allocate a swap entry for it, and it may decrement the reference count associated with any mmap of the page, but it will NOT decrement the refcount associated with the kiobuf itself, and will not evict the page from memory. > > - lock_kiovec() sets the PG_locked flag for the pages in the kiobufs of a kiovec. The PG_locked flag prevents the pages from being swapped out, which is however already > > ensured by map_user_kiobuf(). > > I believe PG_locked will prevent the VM from unmapping the > page, which does, in fact, gaurantee that it won't be > swapped out. The page will not be swapped out anyway. You don't need to lock it to prevent that. Locking may be useful if you want to serialise IO on a particular page, but if you don't need that, there's just no point in locking the pages. Cheers, Stephen -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
