All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: qemu-devel@nongnu.org
Subject: Re: 9pfs developers docs
Date: Thu, 25 Feb 2021 17:47:01 +0100	[thread overview]
Message-ID: <20210225174701.193cf694@bahia.lan> (raw)
In-Reply-To: <1713522.Q2EPVctnWf@silver>

On Thu, 25 Feb 2021 17:31:22 +0100
Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:

> On Montag, 1. Februar 2021 14:37:02 CET qemu_oss--- via wrote:
> > On Montag, 1. Februar 2021 13:26:49 CET Greg Kurz wrote:
> > > > > I agree that a bunch of other things should be documented, but that's
> > > > > definitely a great start. Thanks for doing this !
> > > > > 
> > > > > Just one remark on the topology diagram:
> > > > > 
> > > > > https://wiki.qemu.org/File:9pfs_topology.png
> > > > > 
> > > > > It gives the impression that the 9p transport and server can
> > > > > handle multiple guests, which they certainly don't : each
> > > > > 9p server lives in exactly one device which is exposed to
> > > > > exactly one guest.
> > > > 
> > > > Right, I haven't considered that the diagram might be interpreted that
> > > > way. My primary intention was to show the 3 main components of 9pfs from
> > > > design perspective and secondary showing that multiple guests can share
> > > > storage.
> > > > 
> > > > So what would be better: a) duplicating the server side in the diagram
> > > > (then the image might become a bit large in height), b) dropping the
> > > > multiple guests, c) making the issue with server instances clear in the
> > > > text?
> > > 
> > > I'd rather go for b)
> > 
> > Updated the diagram on the wiki page.
> > 
> > To keep noise low, I won't send emails on further changes to that wiki page.
> > If you want to be auto notified then just add yourself to the watch list
> > there.
> 
> Ok, I think I'm done with this page:
> https://wiki.qemu.org/Documentation/9p
> 
> At least I think I've described everything I wanted to from my side regarding 
> current 9p status.
> 

Great thanks for doing this ! I'll have a look ASAP.

Cheers,

--
Greg


> Best regards,
> Christian Schoenebeck
> 
> 



  reply	other threads:[~2021-02-25 16:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31 18:23 9pfs developers docs Christian Schoenebeck
2021-02-01  9:24 ` Greg Kurz
2021-02-01 11:30   ` Christian Schoenebeck
2021-02-01 12:26     ` Greg Kurz
2021-02-01 13:15       ` Paolo Bonzini
2021-02-01 13:37       ` qemu_oss--- via
2021-02-25 16:31         ` Christian Schoenebeck
2021-02-25 16:47           ` Greg Kurz [this message]
2021-02-01 11:42 ` Peter Maydell
2021-02-01 13:44   ` Christian Schoenebeck

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=20210225174701.193cf694@bahia.lan \
    --to=groug@kaod.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu_oss@crudebyte.com \
    /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.