[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54117D3A.3010305@plexistor.com>
Date: Thu, 11 Sep 2014 13:45:14 +0300
From: Boaz Harrosh <boaz@...xistor.com>
To: Dan Williams <dan.j.williams@...el.com>
CC: Boaz Harrosh <openosd@...il.com>,
Ross Zwisler <ross.zwisler@...ux.intel.com>,
Jens Axboe <axboe@...nel.dk>,
Matthew Wilcox <matthew.r.wilcox@...el.com>,
Nick Piggin <npiggin@...nel.dk>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-nvdimm@...ts.01.org
Subject: Re: [Linux-nvdimm] [PATCH v2] pmem: Initial version of persistent
memory driver
On 09/11/2014 02:01 AM, Dan Williams wrote:
<>
>
> Imagine you want to deploy a policy like "use half of the memory
> provided by the dimm in slot3, i.e. the only one with a battery".
> That sort of thing gets unwieldy in a command line string compared to
> a description table format that we can update at will.
>
Actually it is easy to do, why? I do this here in the lab all the time.
with a "command line" with this code you see here.
[DDR3 NvDIMM which means I need memmap=16G\$32G on Kernel command line.
Then: modprobe pmem map=8G@32G,4G@44G,...
and so on Just as a simple example where 2/4-3/4 addresses are not used.
You can have holes in the middle or what ever you want. This here is just
a table in comma-separated format. If we need like flags in future we can
extend the format to nn@ss:flags, but I do no have any 3rd column yet]
And again I have in the pipe a dynamic interface added on top of
the module param one. So it will all be there soon. Without reverting
the old one.
Thanks
Boaz
--
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