Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S282843AbSAUKng>; Mon, 21 Jan 2002 05:43:36 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S282967AbSAUKnb>; Mon, 21 Jan 2002 05:43:31 -0500
Received: from mail.pha.ha-vel.cz ([195.39.72.3]:59148 "HELO
	mail.pha.ha-vel.cz") by vger.kernel.org with SMTP
	id <S282843AbSAUKnS>; Mon, 21 Jan 2002 05:43:18 -0500
Date: Mon, 21 Jan 2002 11:43:11 +0100
From: Vojtech Pavlik <vojtech@suse.cz>
To: Andre Hedrick <andre@linuxdiskcert.org>
Cc: Davide Libenzi <davidel@xmailserver.org>, Jens Axboe <axboe@suse.de>,
        Anton Altaparmakov <aia21@cam.ac.uk>,
        Linus Torvalds <torvalds@transmeta.com>,
        lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.3-pre1-aia1
Message-ID: <20020121114311.A24604@suse.cz>
In-Reply-To: <Pine.LNX.4.40.0201201054011.7238-100000@blue1.dev.mcafeelabs.com> <Pine.LNX.4.10.10201201555040.12376-100000@master.linux-ide.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.LNX.4.10.10201201555040.12376-100000@master.linux-ide.org>; from andre@linuxdiskcert.org on Sun, Jan 20, 2002 at 04:12:36PM -0800
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Sun, Jan 20, 2002 at 04:12:36PM -0800, Andre Hedrick wrote:

> > > > We only read out 4k thus the device has the the next 4k we may be wanting
> > > > ready.  Look at it as a dirty prefetch, but eventally the drive is going
> > > > to want to go south, thus [lost interrupt]
> > >
> > > Even if the drive is programmed for 16 sectors in multi mode, it still
> > > must honor lower transfer sizes. The fix I did was not to limit this,
> > > but rather to only setup transfers for the amount of sectors in the
> > > first chunk. This is indeed necessary now that we do not have a copy of
> > > the request to fool around with.
> 
> Listen and for just a second okay.
> 
> Since the set multimode command is similar to the set transfer rate, if
> you program the drive to run at U100 but the host can feed only U33 you
> have problems.  Much of this simple arguement is the same answer for
> multimode.
> 
> Same thing here but a variation, of the operations,

So you're saying that if you program the drive to multimode 16, you
can't read a single sector and always have to read 16? That not only
doesn't make sense to me, but it also contradicts anything that I've
heard before.

-- 
Vojtech Pavlik
SuSE Labs
-
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/