[lkml]   [2006]   [Mar]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC PATCH 30/35] Add generic_page_range() function

On 22 Mar 2006, at 14:33, Keir Fraser wrote:

> Okay, can you suggest a better one? That's the best I could come up
> with that wasn't long winded.

How about apply_to_page_range()?

>> secondly, I think you confuse our (confusing) terminology: the page
>> that holds pte_ts is not the pte_page, the pte_page is the page that
>> a pte points to
> What should we call it? Essentially we want to be able to get the
> physical address of a PTE in some cases, and passing struct page
> pointer seemed the best way to be able to derive that. I can rename it
> to something else vaguely plausible if the only problem is the
> semantic clash with Linux's idiomatic use of pte_page.

Looks like pmd_page is correct?

-- Keir

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-03-22 16:38    [W:0.077 / U:29.676 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site