From: Lyle Seaman <lws-RAHWjsxJnJUdnm+yROfE0A@public.gmane.org>
To: Herbert Nachtnebel
<Herbert.Nachtnebel-8zxNtbQCHXIjuwv8T7myQQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: AW: Re: [PATCH] S4bios for 2.5.52.
Date: Thu, 19 Dec 2002 10:05:55 -0500 [thread overview]
Message-ID: <20021219150600.C5DBE1480A@o-o.yi.org> (raw)
In-Reply-To: Message from "Herbert Nachtnebel" <Herbert.Nachtnebel-8zxNtbQCHXIjuwv8T7myQQ@public.gmane.org> of "Thu, 19 Dec 2002 10:49:06 +0100." <B900970C7DD9474C972986EB3EC7C58F0D404E-PWLG29+z7hEKeIAE67mlpo2P0GrZ+RbP@public.gmane.org>
> but that sounds like a unpluged block queue which get flushed every 5 seconds (or 30 seconds) by the bdflush daemon. There are two things which counters this, 1st: swsusp works on ide and there aren't such problems since aeons and 2nd Pavel knows that :-)
> Hence, apologies for this hip shot.
I'm not sure I understand what you're saying, Herbert.
There was something broken in yield() or schedule() back around 2.5.20 -
2.5.40 that made rw_swap_page_sync EXCRUTIATINGLY slow, but that's been fixed.
Still, writing pages synchronously, one at a time, is going to be slow no
matter what you do. *Especially* on slow laptop drives.
What I sent Nigel was a little patch to write them 20 at a time, which reduced
my suspend times from nearly 60 seconds to something around 2 seconds. I
stopped at 20 because going beyond that was chasing diminishing returns and I
didn't think that chewing up a huge chunk of stack was justified for a
one-second reduction in suspend times.
I didn't send it on to the rest of the list because I figure Nigel's other
changes will be coming along as well, and I didn't want to make merging too
difficult for everyone.
-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now! Before the Holidays pass you by.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
next parent reply other threads:[~2002-12-19 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Herbert.Nachtnebel@tuwien.ac.at>
[not found] ` <B900970C7DD9474C972986EB3EC7C58F0D404E-PWLG29+z7hEKeIAE67mlpo2P0GrZ+RbP@public.gmane.org>
2002-12-19 15:05 ` Lyle Seaman [this message]
[not found] ` <20021219150600.C5DBE1480A-RAHWjsxJnJUdnm+yROfE0A@public.gmane.org>
2002-12-19 20:12 ` AW: Re: [PATCH] S4bios for 2.5.52 Nigel Cunningham
2002-12-19 20:04 ` Nigel Cunningham
2002-12-19 9:49 AW: " Herbert Nachtnebel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021219150600.C5DBE1480A@o-o.yi.org \
--to=lws-rahwjsxjnjudnm+yrofe0a@public.gmane.org \
--cc=Herbert.Nachtnebel-8zxNtbQCHXIjuwv8T7myQQ@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox