From: Matthew Wilcox <willy@linux.intel.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Boaz Harrosh <boaz@plexistor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-nvdimm@ml01.01.org, Keith Busch <keith.busch@intel.com>,
Andy Lutomirski <luto@amacapital.net>, Jens Axboe <axboe@fb.com>,
dm-devel@redhat.com, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: Persistent memory interface
Date: Fri, 19 Jun 2015 12:48:25 -0400 [thread overview]
Message-ID: <20150619164825.GB1971@linux.intel.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1506191211480.30318@file01.intranet.prod.int.rdu2.redhat.com>
On Fri, Jun 19, 2015 at 12:33:09PM -0400, Mikulas Patocka wrote:
> If I want to use persistent memory in another driver, for a different
> purpose, how can I make sure that that drivers/block/pmem.c doesn't attach
> to this piece of memory and export it? It seems not possible.
> drivers/block/pmem.c attaches to everything without regard that there may
> be other users of persistent memory.
You need to look at the patches that Dan has been posting to add support
for Labels (and NFIT and ...). Those weren't available earlier because
the label spec wasn't public.
> BTW. some journaling filesystems assume that 512-byte sector is written
> atomically. drivers/block/pmem.c breaks this requirement. Persistent
> memory only gurantees 8-byte atomic writes.
... and that's addressed by the BTT patches.
next prev parent reply other threads:[~2015-06-19 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 16:33 Persistent memory interface Mikulas Patocka
2015-06-19 16:48 ` Matthew Wilcox [this message]
2015-06-19 16:52 ` Mikulas Patocka
2015-06-19 16:50 ` Verma, Vishal L
2015-06-22 16:50 ` Doug Dumitru
2015-06-22 19:01 ` Doug Dumitru
2015-06-22 21:35 ` Verma, Vishal L
2015-06-23 10:21 ` hch
2015-06-22 21:25 ` Verma, Vishal L
2015-06-22 22:17 ` Doug Dumitru
2015-06-19 16:53 ` Doug Dumitru
2015-06-19 17:35 ` Dan Williams
2015-06-19 19:14 ` Mikulas Patocka
2015-06-19 19:22 ` Dan Williams
2015-06-19 19:23 ` Dan Williams
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=20150619164825.GB1971@linux.intel.com \
--to=willy@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=boaz@plexistor.com \
--cc=bp@alien8.de \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=keith.busch@intel.com \
--cc=linux-nvdimm@ml01.01.org \
--cc=luto@amacapital.net \
--cc=mpatocka@redhat.com \
--cc=ross.zwisler@linux.intel.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.