[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4jzHMMWuvWnA5kL0BphVrnaC4TwQfSqsSXN-=qjRpwDWQ@mail.gmail.com>
Date: Wed, 15 Apr 2015 21:31:28 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: Christoph Hellwig <hch@....de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
Ross Zwisler <ross.zwisler@...ux.intel.com>,
Boaz Harrosh <boaz@...xistor.com>,
Matthew Wilcox <matthew.r.wilcox@...el.com>
Subject: Re: [GIT PULL] PMEM driver for v4.1
On Wed, Apr 15, 2015 at 1:45 AM, Ingo Molnar <mingo@...nel.org> wrote:
>
> * Dan Williams <dan.j.williams@...el.com> wrote:
>
>> > None of this gives me warm fuzzy feelings...
>> >
>> > ... has anyone explored the possibility of putting 'struct page'
>> > into the pmem device itself, essentially using it as metadata?
>>
>> Yes, the impetus for proposing the pfn conversion of the block layer
>> was the consideration that persistent memory may have less write
>> endurance than DRAM. The kernel preserving write endurance
>> exclusively for user data and the elimination of struct page
>> overhead motivated the patchset [1].
>>
>> [1]: https://lwn.net/Articles/636968/
>
> (Is there a Git URL where I could take a look at these patches?)
git://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm
evacuate-struct-page-v1
Note that the bulk of the change is automated via Coccinelle.
For v2, I'm looking at enabling a kmap primitive to operate on a
pfn_t, kmap_pfn().
--
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