From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "doug@easyco.com" <doug@easyco.com>
Cc: "Busch, Keith" <keith.busch@intel.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-nvdimm@ml01.01.org" <linux-nvdimm@ml01.01.org>,
"luto@amacapital.net" <luto@amacapital.net>,
"axboe@fb.com" <axboe@fb.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"mpatocka@redhat.com" <mpatocka@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>, "bp@alien8.de" <bp@alien8.de>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"hch@lst.de" <hch@lst.de>
Subject: Re: Persistent memory interface
Date: Mon, 22 Jun 2015 21:35:47 +0000 [thread overview]
Message-ID: <1435008947.32433.82.camel@intel.com> (raw)
In-Reply-To: <CAFx4rwRhmnpDKdhofZp5f7fXQYL1SwW_oQyB_V=M5Gm=W0xGbg@mail.gmail.com>
On Mon, 2015-06-22 at 12:01 -0700, Doug Dumitru wrote:
> ... while you are at it, you should consider supporting other binary
> block sizes.
>
Hm, what would be the use case? We do support a variety of metadata
sizes for protection information [1]. Apart from this, the standard
block sizes of 512 and 4096 are the only ones Linux can support, so I'm
not sure what you mean by other binary block sizes?
-Vishal
[1]: https://lkml.org/lkml/2015/6/17/947
next prev parent reply other threads:[~2015-06-22 21:35 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
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 [this message]
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=1435008947.32433.82.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=bp@alien8.de \
--cc=dm-devel@redhat.com \
--cc=doug@easyco.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=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.