Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S310989AbSCMSzr>; Wed, 13 Mar 2002 13:55:47 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S310990AbSCMSza>; Wed, 13 Mar 2002 13:55:30 -0500
Received: from astound-64-85-224-253.ca.astound.net ([64.85.224.253]:22026
	"EHLO master.linux-ide.org") by vger.kernel.org with ESMTP
	id <S310989AbSCMSzP>; Wed, 13 Mar 2002 13:55:15 -0500
Date: Wed, 13 Mar 2002 10:52:38 -0800 (PST)
From: Andre Hedrick <andre@linux-ide.org>
To: Jens Axboe <axboe@suse.de>
cc: Marcelo Tosatti <marcelo@conectiva.com.br>, Karsten Weiss <knweiss@gmx.de>,
        lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.19-pre3
In-Reply-To: <20020313174007.GB23987@suse.de>
Message-ID: <Pine.LNX.4.10.10203131032220.19703-100000@master.linux-ide.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 13 Mar 2002, Jens Axboe wrote:

> On Wed, Mar 13 2002, Andre Hedrick wrote:
> > > 
> > > Please go on on the third point because coming full circle to see an error.
> > 
> > Well I promised to help you if you got stuck, so here is a hint.
> 
> I'm not stuck, I'm just done arguing with you. I have much better things
> to do than waste my time doing that.
> 
> > Describe the variations between the hardware atomic segment wrt to the
> 
> [snip, class assignment]
> 
> This is not a class and you are definitely not my teacher. I've
> described plenty of times before what the problems are, I don't see why
> this should be any better.

You answers have only addressed BLOCK, you have yet to address the
hardware.  If you think this is a game, it is not.  It is to try and get a
point across so that we can move forward.  It is the same problem you have
in 2.5.  I can post the solution to the hardware atomic.  It does not
address the data integrity violations force upon it.

So if you think this is class fine.  It is really a an issue of shared
learning.  You brought me back up to date on how BLOCK behaves because I
forgot.  All I ma trying to do is bring you up to date on how the hardware
works.  But if you will not communitcate so I can see how far you have the
point in question it will never be resolved.

Also, I know you well enough.  If there is an issue you do/will/can not
address you go quiet.

If you do not understand, I want to help you to.
I accepted your help when you offered it and thanked you for it.

Regards,

Andre Hedrick


-
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/