From: jim@rubylane.com
To: tbrown@baremetal.com (Tom Brown)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Update on Promise 100TX2 + Serverworks IDE issues -- 2.2.20
Date: Wed, 3 Apr 2002 06:52:02 -0800 (PST) [thread overview]
Message-ID: <20020403145202.27388.qmail@london.rubylane.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10204022311020.24257-100000@tom2.baremetal.com> from "Tom Brown" at Apr 02, 2002 11:12:18 PM
>
> On Tue, 2 Apr 2002 jim@rubylane.com wrote:
>
> > >
> > > On Tue, 2 Apr 2002 jim@rubylane.com wrote:
> > > > 2. The MB IDE ports transfer data at about 18000K/sec while doing
> > > > cat /dev/hda >/dev/null and looking at vmstat.
> > >
> > > I think the serverworks IDE is only mode4, not even UDMA33. I heard a lot of
> > > bad things about it, and removed all the IDE drives from our serverworks
> > > system's controller.
> > >
> > > > hdk. In a 32-bit slot, cat /dev/hdx >/dev/null shows 31300K/sec. But
> > > > doing cat /dev/hde4 (a specific partition) for example gives
> > > > 8400K/sec. That makes no sense to me.
> > >
> > > The outer cylinders of a drive are faster than the inner cylinders. Try
> > > repartitioning the drive so that hde4 starts at cylinder 1, and see if that
> > > changes the speed.
> >
> > That's not it because all 4 drives are partitioned the same, yet hde4
> > gives 8400K/sec and hdk4 gives 31000K. Also there are the same number
> > of interrupts/sec and context switches per sec according to vmstat in
> > the 8400 and 31000 case.
>
> sure you've got the same block size? 8400 * 4 is suspiciously close the
> 31000 ... I don't use vmstat, so I'm not sure if it reports blocks or
> kbyte /sec
Yeah, I even remade the file systems on both drives and got the same
result.
After moving the drives around on the Promise controller and moving 1
drive back to the MB IDE port, it looks like all drives are running at
high speed. I dunno - it's weird. I wouldn't be surprised if one of
the drives arbitrarily reverts back to the slower speed at some point
or after a future reboot, though it hasn't yet.
I was thinking maybe burst mode was not getting turned on, not working,
or getting turned off on some of the Promise ports for some reason.
vmstat reports KB/sec.
Jim
next parent reply other threads:[~2002-04-03 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10204022311020.24257-100000@tom2.baremetal.com>
2002-04-03 14:52 ` jim [this message]
2002-04-02 23:38 jim
2002-04-03 0:48 ` Trent Piepho
2002-04-03 1:18 ` Alan Cox
2002-04-03 2:08 ` Jeff Nguyen
2002-04-03 2:58 ` Alan Cox
2002-04-03 2:58 ` jim
2002-04-03 3:10 ` jim
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=20020403145202.27388.qmail@london.rubylane.com \
--to=jim@rubylane.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tbrown@baremetal.com \
/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®