linux-kernel - Re: [PATCH v10 00/21] Support ext4 on NV-DIMMs

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1409263783.27285.7.camel@rzwisler-mobl1.amr.corp.intel.com>
Date:	Thu, 28 Aug 2014 22:09:45 +0000
From:	"Zwisler, Ross" <ross.zwisler@...el.com>
To:	"openosd@...il.com" <openosd@...il.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"willy@...ux.intel.com" <willy@...ux.intel.com>,
	"Wilcox, Matthew R" <matthew.r.wilcox@...el.com>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH v10 00/21] Support ext4 on NV-DIMMs

On Thu, 2014-08-28 at 11:08 +0300, Boaz Harrosh wrote:
> On 08/27/2014 06:45 AM, Matthew Wilcox wrote:
> > One of the primary uses for NV-DIMMs is to expose them as a block device
> > and use a filesystem to store files on the NV-DIMM.  While that works,
> > it currently wastes memory and CPU time buffering the files in the page
> > cache.  We have support in ext2 for bypassing the page cache, but it
> > has some races which are unfixable in the current design.  This series
> > of patches rewrite the underlying support, and add support for direct
> > access to ext4.
> > 
> > Note that patch 6/21 has been included in
> > https://git.kernel.org/cgit/linux/kernel/git/viro/vfs.git/log/?h=for-next-candidate
> > 
> 
> Matthew hi
> 
> Could you please push this to the regular or a new public tree?
> 
> (Old versions are at: https://github.com/01org/prd)
> 
> Thanks
> Boaz

Hi Boaz,

I've pushed the updated tree to https://github.com/01org/prd in the master
branch.  All the older versions of the code that we've had while rebasing are
still available in their own branches.

Thanks,
- Ross