public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Stefan Smietanowski <stesmi@stesmi.com>
Cc: Ben Israel <ben@genesis-one.com>, linux-kernel@vger.kernel.org
Subject: Re: Disk Performance
Date: Fri, 09 Nov 2001 16:50:56 -0700	[thread overview]
Message-ID: <3BEC6BE0.6080503@candelatech.com> (raw)
In-Reply-To: <000201c16963$365e19e0$5101a8c0@pbc.adelphia.net> <3BEC67BB.3000607@stesmi.com>



Stefan Smietanowski wrote:

> Hi.
> 
>> Why does my 40 Megabyte per second IDE drive, transfer files at best 
>> at 1-2
>> Megabytes per second? Can anyone prove that this must be the case? 
>> What is
>> the most efficient way to convince anyone who reads this that it can't be
>> proven because a counter example exists?
>>
>> I wish to be personally CC'ed the answers/comments posted to the list in
>> response to this posting.
>>
>> This is my first attempt at being part of the process. Please give me 
>> some
>> time to adjust.
> 
> 
> 40Megabyte per second you say. Well, if it benchmarks at 1-2 Megabytes 
> per second it sounds like a 2 Megabytes per second drive to me, not a 40 
> Megabytes per second drive.
> 
> But, to try to speed it up, make sure you're running with DMA mode enabled.
> 
> hdparm -d1 /dev/hdx where x = number of drive (a=primary master, 
> b=primary slave, c=secondary master, etc).
> 
> But, apart from that, if it indeed is a real problem, what's the name of 
> the motherboard, chipset, hard drive, what linux kernel revision are you 
> running and do you use any special patches or tricks with it?
> 


I once had a problem where the cable was attached in the middle, and the end was
not attached to anything (the cable supported two drives).  After changing to
the end connector, it went from 2MB to 30+MB....

Ben


> // Stefan
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear



  reply	other threads:[~2001-11-09 23:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-09 21:04 Disk Performance Ben Israel
2001-11-09 22:31 ` Rik van Riel
2001-11-09 22:53   ` Erik Andersen
2001-11-09 22:57     ` Rik van Riel
2001-11-09 23:20       ` Erik Andersen
2001-11-09 23:45         ` Matthias Schniedermeyer
2001-11-11 19:24         ` Maxwell Spangler
2001-11-11 21:52           ` Andre Hedrick
2001-11-11 20:56             ` Maxwell Spangler
2001-11-11 22:17               ` Andre Hedrick
2001-11-12  6:02           ` Erik Andersen
2001-11-09 23:24     ` Alan Cox
2001-11-09 22:35 ` Doug McNaught
2001-11-09 23:33 ` Stefan Smietanowski
2001-11-09 23:50   ` Ben Greear [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-10  1:21 Torrey Hoffman
2001-11-10 16:47 ` Davidovac Zoran
2001-11-10 17:51   ` Erik Andersen
     [not found] <fa.jmrptbv.1dh8ur1@ifi.uio.no>
2001-11-10  8:03 ` Dan Maas

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=3BEC6BE0.6080503@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ben@genesis-one.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stesmi@stesmi.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