From: Christoph Hellwig <hch@infradead.org>
To: "Dilger, Andreas" <andreas.dilger@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Xiong Zhou <jencce.kernel@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peng Tao <bergwolf@gmail.com>, Paul Bolle <pebolle@tiscali.nl>,
Jiri Kosina <trivial@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: [PATCH v2] staging/lustre: lloop depends on BLOCK
Date: Thu, 8 Aug 2013 05:17:47 -0700 [thread overview]
Message-ID: <20130808121747.GA5372@infradead.org> (raw)
In-Reply-To: <CE26E579.5A0ED%andreas.dilger@intel.com>
On Wed, Aug 07, 2013 at 07:45:17AM +0000, Dilger, Andreas wrote:
> The problem still remains that the kernel loop driver eventually depends on
> a local block device for the pages/bios to be written. The Lustre lloop
> driver bypasses the VFS and block layer to generate RPCs from the submitted
> pages to RDMA over the network without a data copy.
No, it doesn't. It still consumes bios just like the regular loop
driver.
Besides missing all kinds of fixes from years of kernel development the
only difference is that it takes a lustre-specific shortcut into the
direct I/O code instead of going through the pagecache.
The patch series I've pointed you to does exactly that in a generic way
and thus superceeds the lloop driver fully.
In case my previous reference was a bit to vague the series starts at:
[PATCH V8 00/33] loop: Issue O_DIRECT aio using bio_vec
please take a look and make sure to review it in case you see any
shortcomings.
prev parent reply other threads:[~2013-08-08 12:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 0:29 [PATCH v2] staging/lustre: lloop depends on BLOCK Xiong Zhou
2013-07-30 7:44 ` Peng Tao
2013-07-31 2:30 ` Xiong Zhou
2013-08-01 0:41 ` Greg Kroah-Hartman
2013-08-02 2:20 ` Xiong Zhou
2013-08-02 3:11 ` Greg Kroah-Hartman
2013-08-01 8:45 ` Christoph Hellwig
2013-08-01 19:57 ` Dilger, Andreas
2013-08-02 10:49 ` Christoph Hellwig
2013-08-07 7:45 ` Dilger, Andreas
2013-08-08 12:17 ` Christoph Hellwig [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=20130808121747.GA5372@infradead.org \
--to=hch@infradead.org \
--cc=andreas.dilger@intel.com \
--cc=bergwolf@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jencce.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=trivial@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).