All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: blkback feature announcement
Date: Mon, 7 Dec 2015 13:42:09 +0100	[thread overview]
Message-ID: <56657EA1.5050008@citrix.com> (raw)
In-Reply-To: <566582EC02000078000BC975@prv-mh.provo.novell.com>

El 07/12/15 a les 13.00, Jan Beulich ha escrit:
> Hello,
> 
> is there a particular reason why "max-ring-page-order" gets written in
> xen_blkbk_probe(), but e.g. "feature-max-indirect-segments" and
> "feature-persistent" get written only in connect(), despite both having
> constant values (and hence the node value effectively being known as
> soon as the device exists)?

No, AFAIK there's no specific reason.

> Or in more general terms: Shouldn't it be well defined at what time
> a frontend can rely on certain nodes to be available for inspection?
> And in doing so, I'd expect the determination to be done such that
> widest flexibility is provided towards the actual implementation, i.e.
> nodes should be written as early as possible. (Of course this applies
> to other frontend/backend pairs too.)

I agree. Regarding blkback the nodes about persistent grants, indirect
descriptors and the ring page order should be written in
xen_blkbk_probe, while the specific information about this virtual disk
(sectors, sector size...) should be written before switching to the
connected state (ie: after hotplug scripts have run).

Roger.

  reply	other threads:[~2015-12-07 12:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07 12:00 blkback feature announcement Jan Beulich
2015-12-07 12:42 ` Roger Pau Monné [this message]
2015-12-07 14:54   ` Konrad Rzeszutek Wilk
2015-12-08  1:08   ` Bob Liu
2015-12-08  8:13     ` Jan Beulich
2015-12-08 11:06       ` Bob Liu
2015-12-08 11:13         ` Jan Beulich
2015-12-08 11:20           ` Bob Liu

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=56657EA1.5050008@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xenproject.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.