lkml.org 
[lkml]   [2006]   [Apr]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Implement lookup_swap_cache for migration entries
Christoph Lameter <clameter@sgi.com> wrote:
>
> On Fri, 14 Apr 2006, Andrew Morton wrote:
>
> > > @@ -305,6 +306,12 @@ struct page * lookup_swap_cache(swp_entr
> > > {
> > > struct page *page;
> > >
> > > + if (is_migration_entry(entry)) {
> > > + page = migration_entry_to_page(entry);
> > > + get_page(page);
> > > + return page;
> > > + }
> >
> > What locking ensures that the state of `entry' remains unaltered across the
> > is_migration_entry() and migration_entry_to_page() calls?
>
> entry is a variable passed by value to the function.

Sigh.

What locking ensures that the state of the page referred to by `entry' is
stable?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-04-14 21:16    [W:0.442 / U:0.600 seconds]
©2003-2014 Jasper Spaans. Advertise on this site