From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] ide_end_drive_cmd(): avoid instruction pipeline stall
Date: Sat, 1 Jul 2006 01:49:50 +0300 [thread overview]
Message-ID: <200607010149.50573.a1426z@gawab.com> (raw)
Alan Cox wrote:
> Ar Gwe, 2006-06-30 am 18:13 +0200, ysgrifennodd Andreas Mohr:
> > Use an independently-formatted "unsigned int" for data instead of a
> > restrictive "u16" to avoid instruction fetch pipeline stalls
> > probably caused by the byte calculations later.
I'm hitting this all the time on 2.6 more so than on 2.4, especially for CPU
bound procs.
> 1. This is a gcc problem
Maybe, but on 2.6, echo 0 > /proc/sys/kernel/randomize_va_space seems to
improve the situation most of the time, although not always.
> 2. Not everyone is using an intel x86-32 box which has such problems
Specifically, 3/4/586 don't show this problem, whereas 686+ show the problem
to varying degrees with slowdown upto 333% on P4.
Can you confirm this?
Thanks!
--
Al
next reply other threads:[~2006-06-30 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 22:49 Al Boldi [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-30 16:13 Andreas Mohr
2006-06-30 17:26 ` Alan Cox
2006-06-30 18:00 ` Andrew Morton
2006-06-30 18:21 ` Alan Cox
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=200607010149.50573.a1426z@gawab.com \
--to=a1426z@gawab.com \
--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
Powered by JetHome