All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linda <lindaj@jma3.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: julien.grall@citrix.com, xen-devel@lists.xenproject.org,
	Wei Liu <wei.liu2@citrix.com>,
	lars.kurth.xen@gmail.com
Subject: Re: clarification of xen Wiki article
Date: Thu, 04 Jun 2015 05:15:57 -0600	[thread overview]
Message-ID: <5570336D.1020401@jma3.com> (raw)
In-Reply-To: <1433411898.7108.97.camel@citrix.com>

On 6/4/2015 3:58 AM, Ian Campbell wrote:
> On Wed, 2015-06-03 at 09:24 -0600, Linda wrote:
>> Hi all,
>>       I was reading
>>
>> http://wiki.xen.org/wiki/XenBus
>>
>> In the section on Store Organization, there is the statement
>> "Information should not be replicated in the store and required to be
>> consistent "  I'm not sure what that means.
>>
>> Can anybody clarify this for me, please?
> This came from the old wiki, so the history is unclear.
>
> I suppose it could mean either:
>
>          If you replicate information in xenstore then you should not
>          expect it to be consistent
>
> or
>
>          Do not replicate information, do not require information to be
>          consistent.
>
> But let me turn the question around: What are you actually trying to
> achieve? i.e. what is causing this ambiguous and confusing statement to
> be a concern for you.
Sometime soon I will be writing a front- and back- end for the 9p fs 
protocol.  (My Outreachy project).  My goall is
to understand where drivers sit logically and physically, so I know what 
I'm doing.  Part of this is to understand Xenbus and Xenstore.

When I know too little, I read carefully, and flag anything I don't 
understand.  For now, I'll ignore this statement.

Thanks, Ian.

Linda Jacobson
>
> Unless the author or someone else in the know speaks up I would propose
> to remove this text from the wiki.
>
> Ian.
>
>

  parent reply	other threads:[~2015-06-04 11:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 17:02 [PATCH v7] libxl: provide libxl_bitmap_{or,and} Linda Jacobson
2015-04-16 14:34 ` Ian Campbell
2015-04-16 14:40   ` Linda
2015-04-16 14:45     ` Wei Liu
2015-04-16 16:49       ` Linda
2015-04-22 14:21         ` Ian Campbell
2015-06-03 15:24 ` clarification of xen Wiki article Linda
2015-06-04  9:58   ` Ian Campbell
2015-06-04 10:35     ` Wei Liu
2015-06-04 11:31       ` Wei Liu
2015-06-04 11:35         ` Ian Campbell
2015-06-04 11:46           ` Wei Liu
2015-06-04 11:15     ` Linda [this message]
2015-06-11  1:45   ` grant tables and driver handshaking Linda
2015-06-11 10:43     ` Wei Liu
2015-06-11 12:32       ` Linda
2015-06-11 16:24         ` Wei Liu
2015-06-11 16:38           ` Ian Campbell
2015-06-11 17:11             ` Linda

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=5570336D.1020401@jma3.com \
    --to=lindaj@jma3.com \
    --cc=ian.campbell@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=lars.kurth.xen@gmail.com \
    --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 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.