From: Carsten Rietzschel <cr7@os.inf.tu-dresden.de>
To: "Saksena, Manas" <Manas.Saksena@timesys.com>
Cc: "Lee Revell" <rlrevell@joe-job.com>,
"Ingo Molnar" <mingo@elte.hu>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"William Lee Irwin III" <wli@holomorphy.com>,
"Lenar L?hmus" <lenar@vision.ee>, "Andrew Morton" <akpm@osdl.org>,
"Arjan van de Ven" <arjanv@redhat.com>,
"Wood, Scott" <Scott.Wood@timesys.com>
Subject: Re: [patch] voluntary-preempt-2.6.8-rc2-L2, preemptable hardirqs
Date: Wed, 28 Jul 2004 22:59:20 +0200 [thread overview]
Message-ID: <200407282259.20577.cr7@os.inf.tu-dresden.de> (raw)
In-Reply-To: <3D848382FB72E249812901444C6BDB1D036EDFD3@exchange.timesys.com>
Hi all,
> i've uploaded -L2:
>
> http://redhat.com/~mingo/voluntary-preempt/voluntary-preempt-2.6.8-rc2-L2
>
While trying to combine voluntary-preempt-2.6.8-rc2-L2 with software suspend 2
(swsusp2) I noticed that:
a) with voluntary-preempt = 3
- writing suspend image to disk is very slow
- resume fails !
b) with voluntary-preempt = 2
- writing suspend image to disk is very slow
- resume works but very slow
c) with voluntary-preempt = 1/0
- all works as expected
It might be interesting for you to test it with suspend(1) / pm_disk (sorry,
these don't work for me). I wonder if they'll also fail.
Regards,
Carsten
next prev parent reply other threads:[~2004-07-28 21:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 3:26 Saksena, Manas
2004-07-28 20:59 ` Carsten Rietzschel [this message]
2004-07-28 22:55 ` Felipe Alfaro Solana
2004-07-29 12:26 ` [patch] voluntary-preempt-2.6.8-rc2-L2 - modem dialup broken Carsten Rietzschel
-- strict thread matches above, loose matches on Subject: below --
2004-07-13 14:24 preempt-timing-2.6.8-rc1 Lenar Lõhmus
2004-07-13 14:39 ` preempt-timing-2.6.8-rc1 William Lee Irwin III
2004-07-25 5:15 ` preempt-timing-2.6.8-rc1 Lee Revell
2004-07-25 22:49 ` preempt-timing-2.6.8-rc1 Lee Revell
2004-07-26 8:23 ` preempt-timing-2.6.8-rc1 Ingo Molnar
2004-07-26 8:29 ` preempt-timing-2.6.8-rc1 Lee Revell
2004-07-26 8:35 ` [patch] voluntary-preempt-2.6.8-rc2-J3 Ingo Molnar
2004-07-26 9:00 ` Lee Revell
2004-07-26 12:40 ` Ingo Molnar
2004-07-26 20:47 ` [patch] voluntary-preempt-2.6.8-rc2-J7 Ingo Molnar
2004-07-27 16:27 ` [patch] voluntary-preempt-2.6.8-rc2-L2, preemptable hardirqs Ingo Molnar
2004-07-27 22:30 ` Felipe Alfaro Solana
2004-07-28 4:55 ` Ingo Molnar
2004-07-27 22:47 ` Lee Revell
2004-07-28 5:05 ` Ingo Molnar
2004-07-28 11:44 ` Thomas Charbonnel
2004-07-28 14:26 ` Ingo Molnar
2004-07-28 15:08 ` Thomas Charbonnel
2004-07-28 20:03 ` Lee Revell
2004-07-28 21:50 ` Lee Revell
2004-07-28 22:32 ` Bill Huey
2004-07-29 1:08 ` Lee Revell
2004-07-29 1:56 ` Lee Revell
2004-07-29 18:04 ` Ingo Molnar
2004-07-29 19:43 ` Lee Revell
2004-07-27 22:57 ` Lee Revell
2004-07-28 4:59 ` Ingo Molnar
2004-07-28 6:18 ` Lee Revell
2004-07-27 23:32 ` Lee Revell
2004-07-27 23:41 ` Dmitry Torokhov
2004-07-28 4:51 ` Ingo Molnar
2004-07-28 1:57 ` Lee Revell
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=200407282259.20577.cr7@os.inf.tu-dresden.de \
--to=cr7@os.inf.tu-dresden.de \
--cc=Manas.Saksena@timesys.com \
--cc=Scott.Wood@timesys.com \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=lenar@vision.ee \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
--cc=wli@holomorphy.com \
/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
all inboxes | Powered by JetHome®