Messages in this thread | | | Date | Wed, 26 Jul 2006 12:08:07 +0200 | From | Pavel Machek <> | Subject | Re: swsusp status report |
| |
On Tue 2006-07-25 11:11:45, Dave Jones wrote: > On Tue, Jul 25, 2006 at 01:25:14PM +0200, Rafael J. Wysocki wrote: > > > V. Freeing memory > > > > Step (3) of the suspend procedure is completed by calling the same > > functions that are normally used by kswapd, but in a slightly different way. > > The part of swsusp responsible for that is referred to as 'the memory > > shrinker' and it may sometimes be called by the suspend-to-RAM code as well > > This isn't actually necessary though is it ? > (Ie, it's a bug that needs fixing?)
Well, it is "nice" to the drivers to let them do their work with reasonable ammount of memory free. Of course, it is also bug in the driver if it fails to work in low-memory conditions.
Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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/
| |