From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andi Kleen <ak@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test3-mm1: scheduling while atomic (ext3?)
Date: Wed, 13 Aug 2003 20:53:12 +0200 [thread overview]
Message-ID: <20030813185312.GI21081@wotan.suse.de> (raw)
In-Reply-To: <1060800263.9130.29.camel@dhcp23.swansea.linux.org.uk>
On Wed, Aug 13, 2003 at 07:44:24PM +0100, Alan Cox wrote:
> On Mer, 2003-08-13 at 16:32, Andi Kleen wrote:
> > The AMD slides assume all very big data sets ;-)
> >
> > I would recommend to remove it.
>
> I'll do some timings when I get a moment - the prefetching mmx copy
Microbenchmarks are useless for this. You have to bench the users too,
otherwise you don't recognize the additional cache misses.
> was a win (and faster than the others for small data as well as large
> on the K7-550 (really a K7 not "Athlon" 8)) way back when.
Possible. In my experience the best copy functions vary widly between
different steppings. Just optimizing for a single one is probably
not a good idea, especially not for an very old one
(except when you add dynamic patches for the different steppings, but
then it quickly gets ugly with too many variants)
When in doubt use the more simple function.
-Andi
next prev parent reply other threads:[~2003-08-13 18:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030813045638.GA9713@middle.of.nowhere.suse.lists.linux.kernel>
[not found] ` <20030813014746.412660ae.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <20030813091958.GA30746@gates.of.nowhere.suse.lists.linux.kernel>
[not found] ` <20030813025542.32429718.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <1060772769.8009.4.camel@localhost.localdomain.suse.lists.linux.kernel>
2003-08-13 11:17 ` Andi Kleen
[not found] ` <20030813042544.5064b3f4.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <1060774803.8008.24.camel@localhost.localdomain.suse.lists.linux.kernel>
2003-08-13 12:10 ` Andi Kleen
2003-08-13 12:48 ` Alan Cox
2003-08-13 13:14 ` Andi Kleen
2003-08-13 14:09 ` Alan Cox
2003-08-13 14:20 ` Andi Kleen
2003-08-13 15:20 ` Alan Cox
2003-08-13 15:32 ` Andi Kleen
2003-08-13 18:44 ` Alan Cox
2003-08-13 18:53 ` Andi Kleen [this message]
2003-08-13 16:39 ` Dave Jones
2003-08-13 18:34 ` Alan Cox
2003-08-13 20:12 ` Dave Jones
2003-08-13 18:37 ` Alan Cox
2003-08-13 18:59 richard.brunner
-- strict thread matches above, loose matches on Subject: below --
2003-08-13 4:56 Jurriaan
2003-08-13 8:47 ` Andrew Morton
2003-08-13 9:19 ` Jurriaan on adsl-gate
2003-08-13 9:55 ` Andrew Morton
2003-08-13 11:06 ` Alan Cox
2003-08-13 11:25 ` Andrew Morton
2003-08-13 11:40 ` Alan Cox
2003-08-18 12:08 ` Pavel Machek
2003-08-13 11:06 ` Andi Kleen
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=20030813185312.GI21081@wotan.suse.de \
--to=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®