[lkml]   [2006]   [Feb]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 1/3] compound page: use page[1].lru
    From: Andrew Morton <>
    Date: Sun, 12 Feb 2006 23:12:23 -0800

    > "David S. Miller" <> wrote:
    > >
    > > The ->mapping check is there essentially to hit user mapped pages that
    > > would be modified by the kernel using kernel space memory accesses
    > > other than those done by copy_user_page() and clear_user_page() (and
    > > their brothers copy_user_highpage() and clear_user_highpage() which
    > > just call the former directly on a non-HIGHPAGE platform like
    > > sparc64).
    > The direct-io.c code just does memset. (That's very common - maybe
    > clear_user_highpage_partial() is needed?)

    Yes, something like clear_user_higpage_partial() is definitely needed
    for cases like direct-io.c.

    We have similar handling for when ptrace() uses get_user_pages() and
    tries to write to those pages, via copy_to_user_page() and
    copy_from_user_page(). But those interfaces don't clear memory and
    they only work in the ptrace path, and they are optimized for that
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-02-13 09:02    [W:0.019 / U:116.224 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site