Re: [PATCH][3/3] mm: swsusp post resume aggressive swap prefetch

Hi,

On Sunday 19 March 2006 16:34, Con Kolivas wrote:
> 
> Swsusp reclaims a lot of memory during the suspend cycle and can benefit
> from the aggressive_swap_prefetch mode immediately upon resuming.

It slows down the resume on my box way too much.  Last time it took 10x more
time than actually reading the image.

I think the problem is for the userland suspend (which I use) it's done too early,
when the image pages are still in the swap, so they are taken into consideration
by the aggressive prefetch.  If that really is the case, the solution would be to
trigger the aggressive prefetch from the userland, if needed, after the image
pages have been released.

Greetings,
Rafael
-
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/

---

• Follow-Ups:
  • Re: [PATCH][3/3] mm: swsusp post resume aggressive swap prefetch
    • From: [email protected]

• References:
  • [PATCH][3/3] mm: swsusp post resume aggressive swap prefetch
    • From: Con Kolivas <[email protected]>

• Prev by Date: Kernel panic: Route cache, RCU, possibly FIB trie.
• Next by Date: [GIT PATCH] Driver Core and sysfs stuff for 2.6.16
• Previous by thread: [PATCH][3/3] mm: swsusp post resume aggressive swap prefetch
• Next by thread: Re: [PATCH][3/3] mm: swsusp post resume aggressive swap prefetch
• Index(es):
  • Date
  • Thread

[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]