linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Jens Axboe <axboe@suse.de>
Cc: Anton Altaparmakov <aia21@cantab.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] 2.4 IDE core for 2.5
Date: Tue, 9 Jul 2002 15:13:21 +0200 (MET DST)	[thread overview]
Message-ID: <ageo65$c7f$2@main.gmane.org> (raw)
In-Reply-To: <20020709125656.GC1940@suse.de>


On Tue, 9 Jul 2002, Jens Axboe wrote:

> On Tue, Jul 09 2002, Bartlomiej Zolnierkiewicz wrote:
> >
> > On Tue, 9 Jul 2002, Anton Altaparmakov wrote:
> >
> > > On Tue, 9 Jul 2002, Jens Axboe wrote:
> > > > I've forward ported the 2.4 IDE core (well 2.4.19-pre10-ac2 to be exact)
> > > > to 2.5.25. It consists of 7 separate patches:
> > >
> > > Fantastic! Seeing that the patches are bitkeeper generated, would it be
> > > possible for you to make a repository available with the patches? (on
> > > bkbits perhaps?) Would make it a lot easier for us bitkeeper users just to
> > > pull from your repository... Especially once you update the patches...
> >
> > Okay, tired of fantastic ;-)
> > This forward port has still broken PIO transfer on errors and really
> > borken multi PIO writes, all due to buffer_head -> bio transition in 2.5.
>
> As I wrote in the initial posting, yes multi pio is broken _for multi
> page bio's_. Where does 2.5 break pio transfers on error? If you are
> talking about a 2.4 code base error, then I don't care, you need to tell
> someone else :-)

PIO on error is broken _for multi page bio's_ .

> > Jens, you would better spend your time on enhancing block layer to
> > allow me fixing them cleanly...
>
> I'll fix the bio support issue for pio multi write, it's in the next
> version.

Okay, will see... :)

--
Bartlomiej


  reply	other threads:[~2002-07-09 13:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09 10:22 [PATCH] 2.4 IDE core for 2.5 Jens Axboe
2002-07-09 10:48 ` Anton Altaparmakov
2002-07-09 10:49   ` Jens Axboe
2002-07-09 10:51     ` Vojtech Pavlik
2002-07-09 10:53       ` Jens Axboe
2002-07-09 11:17     ` Jens Axboe
2002-07-09 12:52   ` Bartlomiej Zolnierkiewicz
2002-07-09 12:56     ` Jens Axboe
2002-07-09 13:13       ` Bartlomiej Zolnierkiewicz [this message]
     [not found]       ` <Pine.SOL.4.30.0207091510450.28198-100000@mion.elka.pw.edu.pl>
2002-07-09 13:16         ` Jens Axboe
2002-07-09 11:11 ` Erik Andersen
2002-07-09 11:13 ` Roy Sigurd Karlsbakk
     [not found] ` <200207091313.07199.roy@karlsbakk.net>
2002-07-09 11:20   ` Jens Axboe
2002-07-09 21:43     ` Miles Lane
2002-07-09 11:24   ` Thunder from the hill
2002-07-09 12:43 ` Tobias Rittweiler
2002-07-09 12:48   ` Jens Axboe
2002-07-09 12:54   ` Jens Axboe
2002-07-09 13:31     ` Re[3]: " Tobias Rittweiler
     [not found]   ` <20020709124827.GA1940@suse.de>
2002-07-09 12:57     ` Re[2]: " Tobias Rittweiler
2002-07-09 20:07 ` Andries Brouwer
2002-07-10  5:43   ` Jens Axboe
2002-07-10 11:11     ` [PATCH] 2.4 IDE core for 2.5, #2 (was Re: [PATCH] 2.4 IDE core for 2.5) Jens Axboe
2002-07-12 11:06       ` Andries Brouwer
2002-07-12 11:23         ` IDE Anders Widman
2002-07-11  9:54   ` [PATCH] 2.4 IDE core for 2.5 Rogier Wolff
2002-07-11  9:56     ` Jens Axboe

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='ageo65$c7f$2@main.gmane.org' \
    --to=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=aia21@cantab.net \
    --cc=axboe@suse.de \
    --cc=linux-ide@vger.kernel.org \
    --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).