From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org, jh@suse.cz
Subject: Re: [PATCH] x86-64: memset optimization
Date: Sun, 19 Aug 2007 01:04:30 -0400 [thread overview]
Message-ID: <20070819010430.2c8c31fc@oldman.hemminger.net> (raw)
In-Reply-To: <200708182055.11277.ak@suse.de>
On Sat, 18 Aug 2007 20:55:11 +0200
Andi Kleen <ak@suse.de> wrote:
>
> > The problem is that on x86-64 you are overriding memset()
>
> I don't. You must be looking at old source
>
> asm-x86_64/string.h 2.6.23rc3:
>
> #define __HAVE_ARCH_MEMSET
> void *memset(void *s, int c, size_t n);
>
> I wanted to do the same on i386 too, but there were some minor obstacles.
> The problem is that the out of line fallback i386 memset is currently
> quite dumb and needs to be rewritten to expand the fill char on its
> own like the x86-64 version. Probably best would be just to port
> the x86-64 version. I just hadn't had time for that.
>
> [Patches welcome, but if you do ask me for my old memset test harness]
>
> -Andi
I am looking at current source, built with current (non-experimental) GCC
from Fedora Core 7. If I dissassemble ether_setup, which is
void ether_setup(struct net_device *dev)
{
...
memset(dev->broadcast, 0xFF, ETH_ALEN);
}
I see a tail recursion (jmp) to memset which is the code in arch/x86_64/lib/memset.S
next prev parent reply other threads:[~2007-08-19 16:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 23:34 [PATCH] x86-64: memset optimization Stephen Hemminger
2007-08-18 7:17 ` Eric Dumazet
2007-08-18 9:46 ` Andi Kleen
2007-08-18 14:56 ` Stephen Hemminger
2007-08-18 18:55 ` Andi Kleen
2007-08-19 5:04 ` Stephen Hemminger [this message]
2007-08-19 18:24 ` [discuss] " Andi Kleen
2007-08-20 15:52 ` Stephen Hemminger
2007-08-20 15:51 ` Arjan van de Ven
2007-08-20 17:03 ` Roland Dreier
2007-08-20 18:16 ` Andi Kleen
2007-08-20 18:56 ` Jan Hubicka
2007-08-21 10:16 ` Denys Vlasenko
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=20070819010430.2c8c31fc@oldman.hemminger.net \
--to=shemminger@linux-foundation.org \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=jh@suse.cz \
--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