Hi.
On Mon, 2006-10-23 at 16:20 +0200, Rafael J. Wysocki wrote:
> On Monday, 23 October 2006 16:15, Nick Piggin wrote:
> > Rafael J. Wysocki wrote:
> >
> > > This case is a bit special. I don't think it would be right to require every
> > > device driver writer to avoid modifying RCU pages from the interrupt
> > > context, because that would break the suspend to disk ...
> > >
> > > Besides, if there is an RCU page that we _know_ we can use to store the image
> > > in it, we can just include this page in the image without copying. This
> > > already gives us one extra free page for the rest of the image and we can
> > > _avoid_ creating two images which suspend2 does and which adds a _lot_ of
> > > complexity to the code.
> >
> > If you don't mind me asking... what are these RCU pages you speak of?
> > I couldn't work it out by grepping kernel/power/*
>
> Oops, s/RCU/LRU/g (shame, shame).
>
> Sorry for the confusion.
Ah. I wondered where RCU came into the picture, but was willing to go
with the theory that you knew something I didn't :)
Nigel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]