From: Graham Stoney <greyham@research.canon.com.au>
To: dan@netx4.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Help with string.S
Date: Wed, 16 Aug 2000 17:26:24 +1000 [thread overview]
Message-ID: <399A4220.23A3B0F5@research.canon.com.au> (raw)
Casting our minds back to July, Dan Malek wrote:
> OK, I think I am bailing out here. For some reason, if I remove
> the 'dcbz' instructions on the MPC8xx processor the world is just
> a better place. I don't know why, maybe because of some of the
> TLB mapping, but I can't find a reason.
What was the eventual outcome of this? I've been doing some 2.2.13
kernel profiling on the 860, and __copy_tofrom_user is coming up as a
hotspot.
I tried dropping in the new improved version from
linux-2.4.0-test7-pre4, and none of the 8xx mods are in there: it'l only
work for 32 byte cache lines.
I hacked it around and found the same as you: it won't work with the
dcbz in there, and of course it doesn't run any faster than the old
version without it. It's certainly getting more complex in there, and I
see your point about whether the extra code will actually make it run
any faster, especially on 8xx CPUs with small I-caches. I'd be keen to
test whatever you've come up with to see if it's actually better than
the old 2.2 code on 8xx CPUs.
It sounds like a few people have at least had a shot at adding support
for other than 32 byte cache lines, but none have propagated into the
official kernels; how does that happen anyway?
Thanks,
Graham
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-08-16 7:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-16 7:26 Graham Stoney [this message]
2000-08-16 16:22 ` Help with string.S tom_gall
2000-08-17 0:50 ` Graham Stoney
2000-08-17 19:28 ` Dan Malek
2000-08-18 2:10 ` Kernel TCP performance profiling (was Re: Help with string.S) Graham Stoney
-- strict thread matches above, loose matches on Subject: below --
2000-07-08 22:57 Help with string.S Dan Malek
2000-07-08 23:57 ` Dan Malek
2000-07-10 6:14 ` Daniel Marmier
2000-07-10 15:17 ` David Edelsohn
2000-07-10 22:42 ` Dan Malek
2000-07-11 5:50 ` Daniel Marmier
2000-07-13 18:52 ` Dan Malek
2000-07-11 10:06 ` Adrian Cox
2000-07-11 15:53 ` Dan Malek
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=399A4220.23A3B0F5@research.canon.com.au \
--to=greyham@research.canon.com.au \
--cc=dan@netx4.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).