On the 28th of August 2014 at 09:17, Dave Chinner wrote:
On Wed, Aug 27, 2014 at 02:30:55PM -0700, Andrew Morton wrote:
On Wed, 27 Aug 2014 16:22:20 -0500 (CDT) Christoph Lameter
wrote:
Some explanation of why one would use ext4 instead of, say,
suitably-modified ramfs/tmpfs/rd/etc?
The NVD
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
On Wed, Aug 27, 2014 at 06:30:27PM -0700, Andy Lutomirski wrote:
> 4) No page faults ever once a page is writable (I hope -- I'm not sure
> whether this series actually achieves that goal).
I can't think of a circumstance in which you'd end up taking a page fault
after a writable mapping is establ
On Wed, Aug 27, 2014 at 02:46:22PM -0700, Andrew Morton wrote:
> > > Sat down to read all this but I'm finding it rather unwieldy - it's
> > > just a great blob of code. Is there some overall
> > > what-it-does-and-how-it-does-it roadmap?
> >
> > The overall goal is to map persistent memory / NV-
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 ex
On Wed, Aug 27, 2014 at 02:30:55PM -0700, Andrew Morton wrote:
> On Wed, 27 Aug 2014 16:22:20 -0500 (CDT) Christoph Lameter
> wrote:
>
> > > Some explanation of why one would use ext4 instead of, say,
> > > suitably-modified ramfs/tmpfs/rd/etc?
> >
> > The NVDIMM contents survive reboot and the
On 08/27/2014 02:46 PM, Andrew Morton wrote:
> I assume (because I wasn't told!) that there are two objectives here:
>
> 1) reduce memory consumption by not maintaining pagecache and
> 2) reduce CPU cost by avoiding the double-copies.
>
> These things are pretty easily quantified. And really the
On Wed, 27 Aug 2014 14:30:55 -0700
Andrew Morton wrote:
> On Wed, 27 Aug 2014 16:22:20 -0500 (CDT) Christoph Lameter
> wrote:
>
> > > Some explanation of why one would use ext4 instead of, say,
> > > suitably-modified ramfs/tmpfs/rd/etc?
> >
> > The NVDIMM contents survive reboot and therefor
On Wed, 27 Aug 2014 17:12:50 -0400 Matthew Wilcox wrote:
> On Wed, Aug 27, 2014 at 01:06:13PM -0700, Andrew Morton wrote:
> > On Tue, 26 Aug 2014 23:45:20 -0400 Matthew Wilcox
> > wrote:
> >
> > > One of the primary uses for NV-DIMMs is to expose them as a block device
> > > and use a filesyst
On Wed, 27 Aug 2014 16:22:20 -0500 (CDT) Christoph Lameter
wrote:
> > Some explanation of why one would use ext4 instead of, say,
> > suitably-modified ramfs/tmpfs/rd/etc?
>
> The NVDIMM contents survive reboot and therefore ramfs and friends wont
> work with it.
See "suitably modified". Pres
On Wed, 27 Aug 2014, Andrew Morton wrote:
> Sat down to read all this but I'm finding it rather unwieldy - it's
> just a great blob of code. Is there some overall
> what-it-does-and-how-it-does-it roadmap?
Matthew gave a talk about DAX at the kernel summit. Its a great feature
because this is an
On Wed, Aug 27, 2014 at 01:06:13PM -0700, Andrew Morton wrote:
> On Tue, 26 Aug 2014 23:45:20 -0400 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 w
On Tue, 26 Aug 2014 23:45:20 -0400 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
13 matches
Mail list logo
