Messages in this thread | | | Date | Sat, 16 Oct 2004 18:43:47 +0200 | From | Pavel Machek <> | Subject | Re: swsusp: 8-order allocation failure on demand (update) |
| |
Hi!
> > > > > > > Ok... And I guess it is nearly impossible to trigger this on > demand, > > > > > > > right? > > > > > > > > > > I think it is possible. Seemingly, on my box it's only a question of > > the > > > > > number of apps started. I think I can work out a method to trigger it > > > > > 90% of the time or so. Please let me know if it's worthy of doing. > > > > > > > > Yes, it would certainly help with testing... > > > > Well, I can do that, it seems, 100% of the time. > > > > The method is to do "init 5" (my default runlevel is 3, because vts become > > unreadable after I start X), log into KDE (as a non-root), start some X apps > > at random (eg. I run gkrellm, kmail, konqueror, Mozilla FireFox 32-bit w/ > > Flash plugin, and konsole with "su -") and run updatedb (as root, of > > course). > > To be precise, the method always leads to a failure, but it seems to be either > 8-order or 9-order page allocation failure.
Okay, you could probably pre-allocate 512K block during bootup, then just use that instead of allocating new one during suspend.
Unfortunately that's rather ugly. You'd ~32 bytes per 4K page, that's almost 1% overhead, not nice. Better solution (but more work) is to switch to link-lists or integrate swsusp2. Pavel -- Boycott Kodak -- for their patent abuse against Java. - 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/
| |