All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: hch@infradead.org, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-mm5
Date: Sat, 22 May 2004 11:44:47 +0200	[thread overview]
Message-ID: <20040522094443.GY1952@suse.de> (raw)
In-Reply-To: <20040522093830.GA3532@infradead.org>

On Sat, May 22 2004, hch@infradead.org wrote:
> > +disk-barrier-core.patch
> > +disk-barrier-core-tweaks.patch
> > +disk-barrier-ide.patch
> > +disk-barrier-ide-symbol-expoprt.patch
> > +disk-barrier-ide-warning-fix.patch
> > +disk-barrier-scsi.patch
> > 
> >  Support for IDE and SCSI barriers
> > 
> > +disk-barrier-dm.patch
> > +disk-barrier-md.patch
> > 
> >  Via device mapper and raid as well.
> 
> Some comments on the API and the SCSI part:
> 
>  - issue_flush_fn prototype choice is bad, the request_queue_t argument
>    wile always be disk->queue so it's not needed and only causes
>    confusion.

Agree, it's mutated into place which is probably the reason for the
dupe.

>  - issue_flush sounds a little strange to me, what about cache_flush
>    or sync_cache instead?

Fine with me, I'm notoriously bad at naming.

>  - scsi_drive.issue_flush should take a scsi_device * as first parameter,
>    not struct device * - makes life for bother caller and callee easier.
>  - should probably add a small helper to get the scsi_driver from the
>    gendisk instead of duplicating the code, ala:
> 
> static inline struct scsi_driver *scsi_disk_driver(struct gendisk *disk)
> {
> 	return *(struct scsi_driver **) disk->private_data;
> }

Fine too.

>  - the WCE check should move into sd_sync_cache

Ditto

>  - NULL scsi_disk can't happen for sd_issue_flush, no need to check,
>    and thus the disctinction of sd_issue_flush vs sd_sync_cache can
>    go and sd_shutdown can simply call the cache flush method.

Neat, thanks.

Thanks for the review Christoph!

-- 
Jens Axboe


  reply	other threads:[~2004-05-22  9:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-22  8:36 2.6.6-mm5 Andrew Morton
2004-05-22  9:09 ` 2.6.6-mm5 Jeff Garzik
2004-05-22  9:22   ` 2.6.6-mm5 hch
2004-05-22  9:26     ` 2.6.6-mm5 Andrew Morton
2004-05-22 11:51   ` 2.6.6-mm5 R. J. Wysocki
2004-05-22  9:26 ` 2.6.6-mm5 hch
2004-05-22  9:32   ` 2.6.6-mm5 Andrew Morton
2004-05-22  9:41     ` 2.6.6-mm5 hch
2004-05-22 19:03       ` 2.6.6-mm5 Brian King
2004-05-22  9:38 ` 2.6.6-mm5 hch
2004-05-22  9:44   ` Jens Axboe [this message]
2004-05-22  9:46 ` 2.6.6-mm5 Felipe Alfaro Solana
2004-05-23 15:51   ` 2.6.6-mm5 James Morris
2004-05-22 11:59 ` 2.6.6-mm5 Matthias Andree
2004-05-22 12:19 ` [patch] 2.6.6-mm5: JFFS2_FS_NAND=y compile error Adrian Bunk
2004-05-23  1:01 ` 2.6.6-mm5 Eric W. Biederman
2004-05-23  1:08   ` 2.6.6-mm5 Andrew Morton
2004-05-23  1:15     ` 2.6.6-mm5 Roland Dreier
2004-05-24 16:17       ` 2.6.6-mm5 Matt Mackall
2004-05-24 17:03         ` 2.6.6-mm5 Eric W. Biederman
2004-05-24 17:43           ` 2.6.6-mm5 Roland Dreier
2004-05-25  7:25             ` 2.6.6-mm5 Eric W. Biederman
2004-05-23  2:45     ` 2.6.6-mm5 Eric W. Biederman
2004-05-24 22:11 ` 2.6.6-mm5 (compile stats) John Cherry
2004-05-25 13:53 ` 2.6.6-mm5 Pavel Machek
2004-05-26 12:41 ` 2.6.6-mm5 Anders Gustafsson
2004-05-26 12:49   ` 2.6.6-mm5 Jens Axboe
2004-05-26 12:59     ` 2.6.6-mm5 Anders Gustafsson
2004-05-26 13:03       ` 2.6.6-mm5 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2004-05-22 10:27 2.6.6-mm5 Oleg Nesterov
2004-05-22 18:02 2.6.6-mm5 Adam Radford
     [not found] <1YAd2-6Th-13@gated-at.bofh.it>
     [not found] ` <1YPF4-2hJ-11@gated-at.bofh.it>
     [not found]   ` <1YPOI-2nq-1@gated-at.bofh.it>
     [not found]     ` <1YRdQ-3pu-5@gated-at.bofh.it>
2004-05-23 11:39       ` 2.6.6-mm5 Andi Kleen
2004-05-23 21:32         ` 2.6.6-mm5 Eric W. Biederman
2004-05-24  0:02         ` 2.6.6-mm5 Eric W. Biederman

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=20040522094443.GY1952@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.