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]
Date:	Thu, 1 Aug 2013 19:57:22 +0000
From:	"Dilger, Andreas" <andreas.dilger@...el.com>
To:	Christoph Hellwig <hch@...radead.org>,
	Xiong Zhou <jencce.kernel@...il.com>
CC:	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 2013/08/01 2:45 AM, "Christoph Hellwig" <hch@...radead.org> wrote:

>On Tue, Jul 30, 2013 at 08:29:51AM +0800, Xiong Zhou wrote:
>> From: Xiong Zhou <jencce.kernel@...il.com>
>> 
>> In the lustre client driver, lloop depends on BLOCK. Add an
>> option for this dependence. Last version of this patch makes
>> LUSTRE_FS depends on BLOCK.
>> Remove unnecessary jdb head files which depends on BLOCK.
>
>The driver should be removed, a filesystem has no business bringing
>its own loop driver.

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.

Cheers, Andreas
-- 
Andreas Dilger

Lustre Software Architect
Intel High Performance Data Division


--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ