public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "Mika Penttilä" <mika.penttila@kolumbus.fi>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Chris Mason <mason@suse.com>
Subject: Re: [PATCH] barrier patch set
Date: Sat, 20 Mar 2004 10:55:02 +0100	[thread overview]
Message-ID: <20040320095502.GB2711@suse.de> (raw)
In-Reply-To: <405B3F74.6040706@kolumbus.fi>

On Fri, Mar 19 2004, Mika Penttil? wrote:
> 
> 
> Jens Axboe wrote:
> 
> >On Fri, Mar 19 2004, Mika Penttil? wrote:
> > 
> >
> >>Jens Axboe wrote:
> >>
> >>   
> >>
> >>>Hi,
> >>>
> >>>A first release of a collected barrier patchset for 2.6.5-rc1-mm2. I
> >>>have a few changes planned to support dm/md + sata, I'll do those
> >>>changes over the weekend.
> >>>
> >>>Reiser has the best barrier support, ext3 works but only if things don't
> >>>go wrong. So only attempt to use the barrier feature on ext3 if on ide
> >>>drives, not SCSI nor SATA.
> >>>
> >>>
> >>>
> >>>     
> >>>
> >>What are these brutal pieces...?
> >>
> >>
> >>+static int ide_transform_pc_req(ide_drive_t *drive, struct request *rq)
> >>+{
> >>+ if (rq->cmd[0] != 0x35) {
> >>+ ide_end_request(drive, 0, 0);
> >>+ return 1;
> >>+ }
> >>+
> >>+ if (!drive->wcache) {
> >>+ ide_end_request(drive, 1, 0);
> >>+ return 1;
> >>+ }
> >>+
> >>+ ide_fill_flush_cmd(drive, rq);
> >>+ return 0;
> >>+}
> >>
> >>
> >>/*
> >>+ * basic transformation support for scsi -> ata commands
> >>+ */
> >>+ if (blk_pc_request(rq)) {
> >>+ if (drive->media != ide_disk)
> >>+ goto kill_rq;
> >>+ if (ide_transform_pc_req(drive, rq))
> >>+ return ide_stopped;
> >>+ }
> >>   
> >>
> >
> >Hmm, I thought it was pretty obvious, even just from the naming and
> >comments. Right now, the block layer issued flush without data attached
> >(ie a drive barrier without pinning it to a buffer) comes as a scsi
> >synchronize cache command. I'm going to change this anyways and allow
> >queue hook of a ->issue_flush_fn() that can just tailored to ide or
> >scsi, _or_ dm/md and that sort of thing.
> > 
> >
> I mean other BLOCK_PC requests than SYNCHRONIZE CACHE -> 
> ide_end_request() and ide_stopped.

That's a bug, good catch. Added to fixme list for next release :)

-- 
Jens Axboe


  reply	other threads:[~2004-03-20  9:55 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19 15:35 [PATCH] barrier patch set Jens Axboe
2004-03-19 16:30 ` Mika Penttilä
2004-03-19 18:16   ` Jens Axboe
2004-03-19 18:44     ` Mika Penttilä
2004-03-20  9:55       ` Jens Axboe [this message]
2004-03-19 16:34 ` Jeff Garzik
2004-03-19 18:19   ` Jens Axboe
2004-03-19 23:01   ` Matthias Andree
2004-03-20  0:02     ` Bartlomiej Zolnierkiewicz
2004-03-20  1:48       ` Johannes Stezenbach
2004-03-20  2:13         ` Bartlomiej Zolnierkiewicz
2004-03-20  2:53           ` Johannes Stezenbach
2004-03-20 16:03             ` Bartlomiej Zolnierkiewicz
2004-03-20 11:36           ` Matthias Andree
2004-03-20 16:00             ` Bartlomiej Zolnierkiewicz
2004-03-20 23:36               ` Johannes Stezenbach
2004-03-21  1:33                 ` Bartlomiej Zolnierkiewicz
2004-03-20 18:52       ` Helge Hafting
2004-03-22 11:15         ` Matthias Andree
2004-03-19 23:59   ` Bartlomiej Zolnierkiewicz
2004-03-20  0:14     ` Jeff Garzik
2004-03-20  0:40       ` Bartlomiej Zolnierkiewicz
2004-03-20  0:42         ` Jeff Garzik
2004-03-20  1:24           ` Bartlomiej Zolnierkiewicz
2004-03-20  9:58             ` Jens Axboe
2004-03-20 10:12               ` Jeff Garzik
2004-03-20 10:19                 ` Jens Axboe
2004-03-20 10:37                   ` Jeff Garzik
2004-03-20 16:30                     ` Bartlomiej Zolnierkiewicz
2004-03-21 18:12                       ` Jeff Garzik
2004-03-20 10:21             ` Jeff Garzik
2004-03-20 15:54               ` Bartlomiej Zolnierkiewicz
2004-03-20  0:17     ` Jeff Garzik
2004-03-20  9:53     ` Jens Axboe
2004-03-20 16:23       ` Bartlomiej Zolnierkiewicz
2004-03-20 16:27         ` Jens Axboe
2004-03-20 16:32         ` Chris Mason
2004-03-20 17:05           ` Bartlomiej Zolnierkiewicz
2004-03-20 17:10             ` Chris Mason
2004-03-20 20:16               ` Bartlomiej Zolnierkiewicz
2004-03-21  9:43                 ` Jens Axboe
2004-03-30 16:04             ` Stephen C. Tweedie
2004-03-30 19:19               ` Chris Mason
2004-03-30 21:50                 ` Stephen C. Tweedie
2004-03-30 22:13                   ` Chris Mason
2004-03-31 14:03                     ` Stephen C. Tweedie
2004-03-31 14:27                       ` Chris Mason
2004-03-31 18:28                         ` Ric Wheeler
2004-03-30 22:21                   ` Jeff Garzik
2004-03-30 22:36                     ` Chris Wedgwood
2004-03-30 22:39                       ` Jeff Garzik
2004-03-30 22:41                         ` Chris Wedgwood
2004-03-30 22:40                     ` Bartlomiej Zolnierkiewicz
2004-03-30 22:38                       ` Jeff Garzik
2004-03-31 14:08                     ` Stephen C. Tweedie
2004-03-31 14:21                       ` Chris Mason
2004-03-31 21:26                         ` Jeff Garzik
2004-03-31 22:09                           ` Chris Mason
2004-03-31 21:27                       ` Jeff Garzik
2004-03-19 16:48 ` Marc-Christian Petersen
2004-03-19 18:19   ` Jens Axboe
2004-03-22 11:09 ` Andrew Morton
2004-03-22 11:10   ` 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=20040320095502.GB2711@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=mika.penttila@kolumbus.fi \
    /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