linux-kernel - Re: [PATCH v2] staging/lustre: lloop depends on BLOCK

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130802104930.GB1718@infradead.org>
Date:	Fri, 2 Aug 2013 03:49:30 -0700
From:	Christoph Hellwig <hch@...radead.org>
To:	"Dilger, Andreas" <andreas.dilger@...el.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Xiong Zhou <jencce.kernel@...il.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Peng Tao <bergwolf@...il.com>, Paul Bolle <pebolle@...cali.nl>,
	Jiri Kosina <trivial@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>
Subject: Re: [PATCH v2] staging/lustre: lloop depends on BLOCK

On Thu, Aug 01, 2013 at 07:57:22PM +0000, Dilger, Andreas wrote:
> It provides significant performance improvement for network IO on Lustre.
> It bypasses DLM locking in Lustre and the VFS layer on the client, copying
> in the loop driver, and page-by-page IO submission in the normal IO path.

Part of being upstream is improving existing drivers instead of copy and
pasting them.  Please take a Look at Shaggys in-kernel direct I/O and
loop improvements and submit any incremental improvements ontop of that
one.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/