From: Boaz Harrosh <bharrosh@panasas.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Peng Tao <bergwolf@gmail.com>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
<linux-nfs@vger.kernel.org>, Peng Tao <tao.peng@emc.com>
Subject: Re: [PATCH 1/2] NFS: call block plug around direct write
Date: Tue, 15 May 2012 19:23:19 +0300 [thread overview]
Message-ID: <4FB282F7.5090408@panasas.com> (raw)
In-Reply-To: <20120515160855.GA5911@infradead.org>
On 05/15/2012 07:08 PM, Christoph Hellwig wrote:
> On Tue, May 15, 2012 at 11:38:22PM +0800, Peng Tao wrote:
>> We bypass generic_file_aio_write() but would want to call block plug.
>
> We in this case is the pnfs block driver at most. Thus these should
> be pnfs block code.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
I thought so too.
But reading the code more closely it might be hard for the blocklayout
to figure out the right state to call these two. Specially the call to
blk_finish_plug(). So you might need to add a new LD API such as
LD()->finish_plug() which is empty for others.
But again inspecting the code it looks like blk_start_plug() is a no-op
and blk_finish_plug() is specially optimized for the empty case.
So is it worth it, the extra effort? I do understand the temptation
to get lazy here.
Just my $0.017
Boaz
next prev parent reply other threads:[~2012-05-15 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 15:38 [PATCH 1/2] NFS: call block plug around direct write Peng Tao
2012-05-15 15:38 ` [PATCH 2/2] NFS: call block plug around direct read Peng Tao
2012-05-16 17:12 ` Myklebust, Trond
2012-05-15 16:08 ` [PATCH 1/2] NFS: call block plug around direct write Christoph Hellwig
2012-05-15 16:23 ` Boaz Harrosh [this message]
2012-05-16 0:35 ` Peng Tao
2012-05-16 7:43 ` Boaz Harrosh
2012-05-16 17:12 ` Myklebust, Trond
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=4FB282F7.5090408@panasas.com \
--to=bharrosh@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bergwolf@gmail.com \
--cc=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tao.peng@emc.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.