mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alessandro Suardi" <alessandro.suardi@gmail.com>
To: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
Cc: "Andreas Mohr" <andi@rhlx01.fht-esslingen.de>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 40% IDE performance regression going from FC3 to FC5 with same kernel
Date: Wed, 12 Apr 2006 00:06:13 +0200	[thread overview]
Message-ID: <5a4c581d0604111506j5f6d0a05y1666e6a7705d7905@mail.gmail.com> (raw)
In-Reply-To: <5a4c581d0604111249g57882f7g29e132a7f4c0ab38@mail.gmail.com>

On 4/11/06, Alessandro Suardi <alessandro.suardi@gmail.com> wrote:
> On 4/11/06, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
> > >> > I'll be filing a FC5 performance bug for this but would like an opinion
> > >> >  from the IDE kernel people just in case this has already been seen...
> > >> >
> > >> > I just upgraded my home K7-800, 512MB RAM box from FC3 to FC5
> > >> >  and noticed a disk performance slowdown while copying files around.
> > >>
> > >> Just another suggestion: try eliminating/pinpointing I/O scheduler issues
> > >> (switch e.g. to "noop" at /sys/block/hda/queue/scheduler and compare again)
> > >
> > >Thanks Andi. Tried every scheduler (my default is anticipatory) and
> > > there aren't meaningful differences - 18.3 to 18.6MB/s.
> > >
> > >As a further data point, my box can burn a 8x DVD+R at up to 7.1x
> > > average speed under FC3, while it barely keeps up with 4x in FC5.
> >
> > Since you said it happens with the same kernel, I think it's caused by
> > userspace (do the boot-with-"-b" thing and you'll know). Possible someone
> > setting DMA to speeds as low as udma4 or udma2.
>
> Booting into /sbin/init -b indeed shows I get 33.3MB/s from hdparm,
>  as in FC3. DMA is (again according to hdparm) udma4 both booted
>  normally and in emergency mode. Note that at this point I'm testing
>  2.6.17-rc1-git4 in FC5, not to be trailing current kernels too much
>  (and yes, I already tested that normal 2.6.17-rc1-git4 boot in FC5
>  gets 18.5MB/s - without IDE_GENERIC, so that is also clearly a
>  non relevant factor).
>
> As per Bill Davidsen's question in another email, blockdev --getra
>  shows 256, which is the same value that hdparm shows.
>

Filed bugzilla #188630.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188630

Thanks,

--alessandro

 "Dreamer ? Each one of us is a dreamer. We just push it down deep because
   we are repeatedly told that we are not allowed to dream in real life"
     (Reinhold Ziegler)

  reply	other threads:[~2006-04-11 22:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-08 14:47 Alessandro Suardi
2006-04-08 15:34 ` Alessandro Suardi
2006-04-08 15:45   ` Arjan van de Ven
2006-04-08 16:27     ` Alessandro Suardi
2006-04-08 16:36       ` Arjan van de Ven
2006-04-08 17:07         ` Alessandro Suardi
2006-04-11 11:26           ` Jan Engelhardt
2006-04-11 18:04             ` Alessandro Suardi
2006-04-11 18:41               ` Jan Engelhardt
2006-04-11 12:28 ` Andreas Mohr
2006-04-11 18:11   ` Alessandro Suardi
2006-04-11 18:43     ` Jan Engelhardt
2006-04-11 19:49       ` Alessandro Suardi
2006-04-11 22:06         ` Alessandro Suardi [this message]
2006-04-11 19:31 ` Bill Davidsen

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=5a4c581d0604111506j5f6d0a05y1666e6a7705d7905@mail.gmail.com \
    --to=alessandro.suardi@gmail.com \
    --cc=andi@rhlx01.fht-esslingen.de \
    --cc=jengelh@linux01.gwdg.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®