linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: Blockbusting news, results end
Date: Mon, 27 Oct 2003 18:03:56 -0800	[thread overview]
Message-ID: <20031028020356.GN8540@pegasys.ws> (raw)
In-Reply-To: <20031027225727.GI8540@pegasys.ws>

On Mon, Oct 27, 2003 at 02:57:27PM -0800, jw schultz wrote:
> On Mon, Oct 27, 2003 at 02:27:09PM -0800, Andre Hedrick wrote:
> > 
> > To date IDEMA has not released a formal spec for drive makers to switch to
> > 4Kb sectors.  If they have, then when running in compatibility mode, a
> > heavy read-modify-write happens to goto the pseudo sector of 512b.
> > 
> > Linux can not handled new IDEMA calls currently.
> 
> Irrelevant!

Andre, if you were trying to say what i am about to, i
apologise.

> I am assuming that these numbers are applicable (one is
> unknown):
> 	logical sector size == 512B
> 	physical sector size == ???B
> 	page size/filesystem block size == 4KB

I have dialoged with Eric Mudama.  He is 99% sure that no
manufacturer of is making ATA drives with physical sectors
larger than 512B.  I'll let that statement trump Norman
Diamond's until i hear otherwise.

The drive manufacturers would like to be able to go to a
larger physical sector but the read-modify-write is just too
scary.  If they could be sure of market acceptance of drives
that required all I/O to be in larger units they would build
them because it would allow greater capacity (and i'm
guessing speed as well) on the same physical hardware.
I look forward to the day with Linux has enough market-share
to influence the hardware manufacturers.

In any case, unless someone can authoritatively contradict
Eric we can ignore the firmware read-modify-write
implications of unreadable sectors.

End-of-subthread!
or in the words of Emily Latella "Never-mind".


  reply	other threads:[~2003-10-28  2:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-26  8:49 Blockbusting news, results end Norman Diamond
2003-10-26  9:22 ` Pavel Machek
2003-10-26 11:25   ` Norman Diamond
2003-10-27 20:58     ` jw schultz
2003-10-27 22:27       ` Andre Hedrick
2003-10-27 22:57         ` jw schultz
2003-10-28  2:03           ` jw schultz [this message]
2003-10-26 11:01 ` Hans Reiser
2003-10-26 12:59   ` Oleg Drokin
2003-10-26 12:05     ` Hans Reiser
2003-10-26 12:39       ` Oleg Drokin
2003-10-26 16:26         ` Hans Reiser
2003-10-26 17:13           ` Oleg Drokin
2003-10-26 18:20             ` Hans Reiser
2003-10-26 19:07               ` Oleg Drokin
2003-10-27 12:44                 ` Vitaly Fertman
2003-10-26 18:39 Mudama, Eric
2003-10-27  9:45 ` Norman Diamond
2003-10-27 10:48   ` Krzysztof Halasa
2003-10-27 17:50 Mudama, Eric
2003-10-28 11:31 Norman Diamond
2003-10-28 16:10 Mudama, Eric
2003-10-28 18:30 ` 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=20031028020356.GN8540@pegasys.ws \
    --to=jw@pegasys.ws \
    --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;
as well as URLs for NNTP newsgroup(s).