From: Borislav Petkov <bp@alien8.de>
To: Lan Tianyu <tianyu.lan@intel.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, toshi.kani@hp.com, imammedo@redhat.com,
jan.kiszka@siemens.com, mingo@kernel.org,
huawei.libin@huawei.com, prarit@redhat.com,
linux-kernel@vger.kernel.org, "Brandt,
Todd E" <todd.e.brandt@intel.com>
Subject: Re: [PATCH] X86/CPU: Avoid 100ms sleep for cpu offline during S3
Date: Tue, 5 Aug 2014 09:54:19 +0200 [thread overview]
Message-ID: <20140805075419.GA18234@pd.tnic> (raw)
In-Reply-To: <53E04457.2060507@intel.com>
Hi Tianyu,
On Tue, Aug 05, 2014 at 10:41:27AM +0800, Lan Tianyu wrote:
> Thanks for your review. We are doing S2RAM optimization.
> We usually use AnalyzeSuspend tool from Brandt, Todd E to observe
> the time consume during S2RAM.(https://github.com/01org/suspendresume.git)
>
> I attached the original result from the tool which showed cpu offline consumes
> more than 100ms. This is due to msleep in the native_cpu_die(). The
> improvement.html shows the test result with the patch. You can't find cpu
> offline at first glance and need to click zoom-in button because the consume
> time of cpu offline is reduced to less than 5ms.
The fact that I can't find it is a good thing, right? :-)
Ok, this looks nice, it actually shows an improvement from cpus going
offline for about 100ish msec and that duration shrinking down to 1.5
msec on average which is a ~100x improv in my book.
And the total S/R time diff looks really good too.
Can people do those measurements outside of your lab? Because if they
can, I could do some on my boxes here too :)
Now, what you could do is run this on a couple of systems, if possible,
write down in the commit message how exactly you did it and add some
relevant numbers to show the speedup. Because this completion thing is
definitely worth pursuing further, provided it doesn't break suspend in
some weird ways.
Btw, the original patches which added the 100ms msleep are:
ef6e525393db ("[PATCH] x86_64: Use msleep in smpboot.c")
aeb8397b6a28 ("[PATCH] i386/smpboot: use msleep() instead of schedule_timeout()")
and its commit message is, of course, :-( not very telling. WTF does
"task delays as expected" mean? I have to go poke peterz for an idea
what it might've meant...
So do you see what I mean with writing a good, verbose commit message,
explaining the situation?
It needs to explain not what we did but why we did it years from now so
that we know exactly if we have to go touch that code again.
HTH.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-08-05 7:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 8:59 [PATCH] X86/CPU: Avoid 100ms sleep for cpu offline during S3 Lan Tianyu
2014-08-04 10:23 ` Borislav Petkov
[not found] ` <53E04457.2060507@intel.com>
2014-08-05 7:54 ` Borislav Petkov [this message]
2014-08-05 9:29 ` Lan Tianyu
2014-08-06 11:07 ` Borislav Petkov
2014-08-06 13:13 ` Lan, Tianyu
2014-08-06 13:57 ` Gene Heskett
2014-08-07 8:47 ` Lan Tianyu
2014-08-07 10:23 ` Gene Heskett
2014-08-06 16:06 ` Borislav Petkov
2014-08-07 8:56 ` Lan Tianyu
2014-08-05 8:41 ` Borislav Petkov
2014-08-05 9:28 ` Lan Tianyu
2014-08-12 7:31 ` [PATCH V2] " Lan Tianyu
2014-08-12 7:55 ` Borislav Petkov
2014-08-12 11:36 ` Prarit Bhargava
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=20140805075419.GA18234@pd.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=huawei.libin@huawei.com \
--cc=imammedo@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=tglx@linutronix.de \
--cc=tianyu.lan@intel.com \
--cc=todd.e.brandt@intel.com \
--cc=toshi.kani@hp.com \
--cc=x86@kernel.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