qemu-devel.nongnu.org archive mirror
 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: Mon, 1 Feb 2021 10:24:26 +0100	[thread overview]
Message-ID: <20210201102426.3a3623c7@bahia.lan> (raw)
In-Reply-To: <3475760.T70ipHyFzN@silver>

On Sun, 31 Jan 2021 19:23:52 +0100
Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:

> Hi,
> 

Hi Christian,

> I started setting up some developer documentation for 9pfs:
> 
> 	https://wiki.qemu.org/Documentation/9p
> 
> Still quite a bunch that should be added (e.g. there should be a section about 
> threads and coroutines), but at least it's a start ...
> 

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.

Cheers,

--
Greg

> Best regards,
> Christian Schoenebeck
> 
> 
> 
> 



  reply	other threads:[~2021-02-01  9:25 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 [this message]
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
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=20210201102426.3a3623c7@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 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).