From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Lin Yongting <linyongting@huawei.com>
Cc: ross.zwisler@linux.intel.com, dan.j.williams@intel.com,
axboe@fb.com, akpm@linux-foundation.org, richard@nod.at,
willy@linux.intel.com, wangxiaozhe@huawei.com, mingo@kernel.org,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pramdisk: new block disk driver to perform persistent storage
Date: Fri, 18 Sep 2015 10:18:13 -0600 [thread overview]
Message-ID: <20150918161813.GA4274@linux.intel.com> (raw)
In-Reply-To: <1442562390-91051-1-git-send-email-linyongting@huawei.com>
On Fri, Sep 18, 2015 at 03:46:30PM +0800, Lin Yongting wrote:
> In embed devices, user space applications will use reserved memory
> (i.e. persistent memory) to store business data, the data is kept
> in this memory region after system rebooting or panic.
>
> pramdisk is a block disk driver based on Persistent memory, it provide
> file system interface for application to read/write data in persistent
> memory. Application can use pramdisk to store log file or business data
> in persistent memory in the way of file system operation, avoid operating
> or managing memory directly.
>
> pramdisk support multiple Persistent menory regions and each one is a
> block device named as /dev/pram<N>.
>
> Usage:
> modprobe pramdisk.ko pmem=<size1>@<addr2> [ pmem=<size2>@<addr2> ... ]
>
> For example:
> modprobe pramdisk.ko pmem=20M@2050M pmem=20M@2150M
> mkfs.ext3 /dev/pram1
> mkdir /tmp/test1
> mount -t ext3 /dev/pram1 /tmp/test1
>
> Signed-off-by: Lin Yongting <linyongting@huawei.com>
> Signed-off-by: Wang xiaozhe <wangxiaozhe@huawei.com>
I think you already have this functionality with the PMEM driver and the
memmap=nn[KMG]!ss[KMG] command line parameter? What are you trying to
accomplish with this driver that you can't do with PMEM?
next prev parent reply other threads:[~2015-09-18 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 7:46 Lin Yongting
2015-09-18 16:18 ` Ross Zwisler [this message]
2015-09-18 16:41 ` Dan Williams
2015-09-21 9:35 ` Lin Yongting
2015-09-21 9:30 ` Lin Yongting
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150918161813.GA4274@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linyongting@huawei.com \
--cc=mingo@kernel.org \
--cc=richard@nod.at \
--cc=wangxiaozhe@huawei.com \
--cc=willy@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome