From: Tom Leete <tleete@mountain.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Ford <david@linux.com>, Stephen Frost <sfrost@snowman.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.x and SMP fails to compile (`current' undefined)
Date: Thu, 01 Feb 2001 08:53:59 -0500 [thread overview]
Message-ID: <3A796A77.3B1D3DE4@mountain.net> (raw)
In-Reply-To: <E14OHKN-00047W-00@the-village.bc.nu>
Alan Cox wrote:
>
> We have a very large number of memcpy's of unknown short length (often in
> interrupts) that are close to branches. A lot of
>
> if(foo==NULL)
> return
> memcpy(..
>
> stuff for example.
>
> Im more than happy for someone to do the benches and prove me wrong
Agreed, that is a bad case, and there is overhead for it in my patch. I'm
putting together some metrics, will post results here.
Regards,
Tom
--
The Daemons lurk and are dumb. -- Emerson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-01 13:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 2:53 2.4.x and SMP fails to compile (`current' undefined) David Ford
2001-01-31 3:01 ` Stephen Frost
2001-01-31 4:37 ` David Ford
2001-01-31 7:16 ` Peter Samuelson
2001-01-31 8:03 ` Tom Leete
2001-01-31 10:26 ` Peter Samuelson
2001-01-31 10:48 ` Tom Leete
2001-01-31 11:10 ` Peter Samuelson
2001-01-31 23:01 ` Olaf Titz
2001-01-31 23:38 ` David Lang
2001-02-01 1:11 ` Peter Samuelson
2001-02-01 1:22 ` Alan Cox
2001-02-02 15:12 ` Pavel Machek
2001-01-31 13:29 ` Alan Cox
2001-02-01 7:52 ` Tom Leete
2001-02-01 8:12 ` Andre Hedrick
2001-02-01 13:39 ` Tom Leete
2001-02-01 10:50 ` Alan Cox
2001-02-01 13:53 ` Tom Leete [this message]
2001-01-31 23:26 ` David Lang
2001-02-01 15:04 ` Jeff Garzik
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=3A796A77.3B1D3DE4@mountain.net \
--to=tleete@mountain.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=david@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrost@snowman.net \
/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