From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: [TRIVIAL] kstrdup
Date: 19 Apr 2003 13:45:00 +0200 [thread overview]
Message-ID: <8kAuh4Wmw-B@khms.westfalen.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0304181512220.22901@chaos>
root@chaos.analogic.com (Richard B. Johnson) wrote on 18.04.03 in <Pine.LNX.4.53.0304181512220.22901@chaos>:
> The test for every byte transferred is, quite obviously, correct.
> It is also, quite obviously, non optimum.
Actually, that is very much not obvious.
Especially if you're familiar with architectures where every move has an
implicit test (typically for zero and sign), and so checking for the zero
byte during the move is quite obviously the only sane thing to do - the
version with a count is slower, because the inner loop does more. (Those
architectures typically don't have a REP-style prefix.)
MfG Kai
next prev parent reply other threads:[~2003-04-19 16:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 7:58 Rusty Trivial Russell
2003-04-18 8:10 ` Jeff Garzik
2003-04-18 16:20 ` Linus Torvalds
2003-04-18 16:56 ` Jeff Garzik
2003-04-18 18:00 ` Linus Torvalds
2003-04-18 18:44 ` Jeff Garzik
2003-04-19 4:52 ` Rusty Russell
2003-04-18 18:00 ` Richard B. Johnson
2003-04-18 18:40 ` Jeff Garzik
2003-04-18 19:24 ` H. Peter Anvin
2003-04-18 23:37 ` Alan Cox
2003-04-18 19:29 ` Richard B. Johnson
2003-04-19 11:45 ` Kai Henningsen [this message]
2003-04-19 20:16 ` Ruth Ivimey-Cook
2003-04-19 4:14 ` Rusty Russell
2003-04-19 4:48 ` Jeff Garzik
2003-04-19 8:28 ` Rusty Russell
2003-04-19 12:27 ` Alan Cox
2003-04-19 14:44 ` Bernd Eckenfels
2003-04-20 8:05 ` Rusty Russell
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=8kAuh4Wmw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--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®