All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: jaxboe@fusionio.com, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: use proper interfaces for on-stack plugging
Date: Mon, 04 Apr 2011 16:12:58 -0500	[thread overview]
Message-ID: <1301951578.2630.77.camel@doink> (raw)
In-Reply-To: <20110330110509.GA9507@infradead.org>

On Wed, 2011-03-30 at 07:05 -0400, Christoph Hellwig wrote:
> Add proper blk_start_plug/blk_finish_plug pairs for the two places where
> we issue buffer I/O, and remove the blk_flush_plug in xfs_buf_lock and
> xfs_buf_iowait, given that context switches already flush the per-process
> plugging lists.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Looks good.

Reviewed-by: Alex Elder <aelder@sgi.com>



_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2011-04-04 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 11:05 [PATCH] xfs: use proper interfaces for on-stack plugging Christoph Hellwig
2011-03-30 11:17 ` Jens Axboe
2011-04-04 21:12 ` Alex Elder [this message]

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=1301951578.2630.77.camel@doink \
    --to=aelder@sgi.com \
    --cc=hch@infradead.org \
    --cc=jaxboe@fusionio.com \
    --cc=xfs@oss.sgi.com \
    /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.