On Tue, 2006-03-14 at 12:51 +0100, Pavel Machek wrote: > "we have just > finished big&ugly memory trashing job, can we get our interactivity > back"? Like I'd probably cron-scheduled it just after updatedb The updatedb problem is STILL not solved? I remember someone proposed years ago to have it use fcntl() or fadvise() to tell the kernel that we are about to read every file on the system and to please not wipe the cache - I guess this was never done? Lee - 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/
- Follow-Ups:
- Re: does swsusp suck after resume for you? [was Re: Faster resuming of suspend technology.]
- From: Con Kolivas <kernel@kolivas.org>
- Re: does swsusp suck after resume for you? [was Re: Faster resuming of suspend technology.]
- References:
- Faster resuming of suspend technology.
- From: Jun OKAJIMA <okajima@digitalinfra.co.jp>
- does swsusp suck aftre resume for you? [was Re: [ck] Re: Faster resuming of suspend technology.]
- From: Pavel Machek <pavel@ucw.cz>
- Re: does swsusp suck after resume for you? [was Re: Faster resuming of suspend technology.]
- From: Con Kolivas <kernel@kolivas.org>
- Re: does swsusp suck after resume for you? [was Re: Faster resuming of suspend technology.]
- From: Con Kolivas <kernel@kolivas.org>
- Re: does swsusp suck after resume for you? [was Re: Faster resuming of suspend technology.]
- From: Pavel Machek <pavel@suse.cz>
- Faster resuming of suspend technology.
- Prev by Date: Re: [PATCH ] drivers/base/bus.c - export reprobe
- Next by Date: Re: [PATCH] Fix SCO on Broadcom Bluetooth adapters
- Previous by thread: Re: does swsusp suck after resume for you? [was Re: Faster resuming of suspend technology.]
- Next by thread: Re: does swsusp suck after resume for you? [was Re: Faster resuming of suspend technology.]
- Index(es):
 |