From: Juergen Gross <jgross@suse.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
tim@xen.org, julien.grall@arm.com, jbeulich@suse.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 2/3] docs: add DIRECTORY_PART specification do xenstore protocol doc
Date: Mon, 8 May 2017 12:31:32 +0200 [thread overview]
Message-ID: <f7312a23-ab5c-46b9-5dd0-a0c4466bb748@suse.com> (raw)
In-Reply-To: <22800.17389.689758.180542@mariner.uk.xensource.com>
On 08/05/17 12:09, Ian Jackson wrote:
> Juergen Gross writes ("[PATCH 2/3] docs: add DIRECTORY_PART specification do xenstore protocol doc"):
>> DIRECTORY_PART was missing in docs/misc/xenstore.txt. Add it.
> ...
>> +DIRECTORY_PART <path>|<offset> <gencnt>|<child-leaf-name>|*
>> + Same as DIRECTORY, but to be used for children lists longer than
>> + XENSTORE_PAYLOAD_MAX. Input are <path> and the byte offset into
>> + the list of children to return. Return values are the generation
>> + count <gencnt> of the node (to be used to ensure the node hasn't
>> + changed between two reads: <gencnt> being the same for multiple
>> + reads guarantees the node hasn't changed) and the list of children
>> + starting at the specified <offset> of the complete list.
>
> The "generation count" is not defined anywhere else in this protocol
> spec, so shouldn't be referred to here without definition. We should
> explicitly state whether using a transaction is sufficient to ensure
> that this check will never fail.
As the generation count is if no interest anywhere else in this protocol
I don't see why the definition given in parentheses isn't enough.
The solution with <gencnt> was explicitly demanded in order to _not_
have to use transactions. So referring to transactions now seems to be
counterproductive.
> Taken together, I think the right approach is to specify a method to
> use this and to say that if a different method is used, the results
> are not reliable.
So libxenstore is using DIRECTORY_PART without transactions and will
still deliver correct results.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-08 10:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 7:00 [PATCH 0/3] docs: add some missing xenstore documentation Juergen Gross
2017-05-08 7:00 ` [PATCH 1/3] docs: specify endianess of xenstore protocol header Juergen Gross
2017-05-08 7:00 ` [PATCH 2/3] docs: add DIRECTORY_PART specification do xenstore protocol doc Juergen Gross
2017-05-08 10:09 ` Ian Jackson
2017-05-08 10:31 ` Juergen Gross [this message]
2017-05-08 11:53 ` Ian Jackson
2017-05-08 12:33 ` Juergen Gross
2017-05-08 7:00 ` [PATCH 3/3] docs: document CONTROL command of xenstore protocol Juergen Gross
2017-05-08 10:13 ` Ian Jackson
2017-05-08 10:22 ` Juergen Gross
2017-05-08 10:39 ` [PATCH 0/3] docs: add some missing xenstore documentation Julien Grall
-- strict thread matches above, loose matches on Subject: below --
2017-05-08 6:58 Juergen Gross
2017-05-08 6:58 ` [PATCH 2/3] docs: add DIRECTORY_PART specification do xenstore protocol doc Juergen Gross
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=f7312a23-ab5c-46b9-5dd0-a0c4466bb748@suse.com \
--to=jgross@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).