All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Xiao Guangrong <guangrong.xiao@linux.intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Juergen Gross <JGross@suse.com>
Subject: Re: [RFC Design Doc v2] Add vNVDIMM support for Xen
Date: Thu, 4 Aug 2016 10:51:52 -0400	[thread overview]
Message-ID: <20160804145152.GC8847@char.us.oracle.com> (raw)
In-Reply-To: <20160804093512.gylpklslammkld3z@hz-desktop>

On Thu, Aug 04, 2016 at 05:35:12PM +0800, Haozhong Zhang wrote:
> On 08/04/16 03:25, Jan Beulich wrote:
> > >>> On 04.08.16 at 10:52, <haozhong.zhang@intel.com> wrote:
> > > On 08/03/16 17:25, Konrad Rzeszutek Wilk wrote:
> > >> Anyhow, wouldn't this 'sizeof(struct page_info)' depend on the ndctl
> > >> tool and what version was used to create this? What if one version
> > >> used 32-bytes for a PAGE, while another used 64-bytes for a PAGE too?
> > >> It would be a bit of catching up .. wait, this same problem MUST
> > >> be with Linux? How does it deal with this?
> > > 
> > > Good question. Linux chooses a size (64 bytes) larger than its current
> > > sizeof(struct page) (40 bytes). We may also do in the same way,
> > > e.g. 32 bytes vs. 64 bytes?
> > 
> > I don't understand this: These structures aren't meant to be
> > persistent, so their size shouldn't matter?
> > 
> 
> But the size of the reserved area is persistent. If the size of struct
> page_info increases in future versions, the reserved area which is
> just enough for old version struct page_info would not be enough for
> the new version.

Exactly!!

Thanks!

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-08-04 14:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18  0:29 [RFC Design Doc v2] Add vNVDIMM support for Xen Haozhong Zhang
2016-07-18  8:36 ` Tian, Kevin
2016-07-18  9:01   ` Zhang, Haozhong
2016-07-19  0:58     ` Tian, Kevin
2016-07-19  2:10       ` Zhang, Haozhong
2016-07-19  1:57 ` Bob Liu
2016-07-19  2:40   ` Haozhong Zhang
2016-08-02 14:46 ` Jan Beulich
2016-08-03  6:54   ` Haozhong Zhang
2016-08-03  8:45     ` Jan Beulich
2016-08-03  9:37       ` Haozhong Zhang
2016-08-03  9:47         ` Jan Beulich
2016-08-03 10:08           ` Haozhong Zhang
2016-08-03 10:18             ` Jan Beulich
2016-08-03 21:25 ` Konrad Rzeszutek Wilk
2016-08-03 23:16   ` Konrad Rzeszutek Wilk
2016-08-04  1:51     ` Haozhong Zhang
2016-08-04  8:52   ` Haozhong Zhang
2016-08-04  9:25     ` Jan Beulich
2016-08-04  9:35       ` Haozhong Zhang
2016-08-04 14:51         ` Konrad Rzeszutek Wilk [this message]
2016-08-04 14:51     ` Konrad Rzeszutek Wilk
2016-08-05  6:25       ` Haozhong Zhang
2016-08-05 13:29         ` Konrad Rzeszutek Wilk

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=20160804145152.GC8847@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=JGross@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=sstabellini@kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.