From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <54117D3A.3010305@plexistor.com> Date: Thu, 11 Sep 2014 13:45:14 +0300 From: Boaz Harrosh MIME-Version: 1.0 Subject: Re: [Linux-nvdimm] [PATCH v2] pmem: Initial version of persistent memory driver References: <1409173922-7484-1-git-send-email-ross.zwisler@linux.intel.com> <1409173922-7484-2-git-send-email-ross.zwisler@linux.intel.com> <540F2977.7010006@plexistor.com> <541050E5.60502@gmail.com> <54108ECA.6090200@plexistor.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org To: Dan Williams Cc: Boaz Harrosh , Ross Zwisler , Jens Axboe , Matthew Wilcox , Nick Piggin , linux-fsdevel , "linux-kernel@vger.kernel.org" , linux-nvdimm@lists.01.org List-ID: 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754260AbaIKKpW (ORCPT ); Thu, 11 Sep 2014 06:45:22 -0400 Received: from mail-pa0-f44.google.com ([209.85.220.44]:43389 "EHLO mail-pa0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754229AbaIKKpU (ORCPT ); Thu, 11 Sep 2014 06:45:20 -0400 Message-ID: <54117D3A.3010305@plexistor.com> Date: Thu, 11 Sep 2014 13:45:14 +0300 From: Boaz Harrosh User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 MIME-Version: 1.0 To: Dan Williams CC: Boaz Harrosh , Ross Zwisler , Jens Axboe , Matthew Wilcox , Nick Piggin , linux-fsdevel , "linux-kernel@vger.kernel.org" , linux-nvdimm@ml01.01.org Subject: Re: [Linux-nvdimm] [PATCH v2] pmem: Initial version of persistent memory driver References: <1409173922-7484-1-git-send-email-ross.zwisler@linux.intel.com> <1409173922-7484-2-git-send-email-ross.zwisler@linux.intel.com> <540F2977.7010006@plexistor.com> <541050E5.60502@gmail.com> <54108ECA.6090200@plexistor.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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