qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Liu Ping Fan <qemulist@gmail.com>
Cc: mdroth <mdroth@linux.vnet.ibm.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] port network layer onto glib
Date: Wed, 13 Mar 2013 11:58:50 +0100	[thread overview]
Message-ID: <51405BEA.6080109@redhat.com> (raw)
In-Reply-To: <1363154346-14827-1-git-send-email-qemulist@gmail.com>

Il 13/03/2013 06:59, Liu Ping Fan ha scritto:
> These series aim to port network backend onto glib, and
> prepare for moving towards making network layer mutlit-thread.
> The brief of the whole aim and plan is documented on 
> http://wiki.qemu.org/Features/network_reentrant
> 
> In these series, attach each NetClientState with a GSource
> At the first, I use AioContext instead of GSource, but after discussion,
> I think with GSource, we can integrated with glib more closely.

Integrating with glib by itself is pointless.  What is the *benefit*?

We have a pretty good idea of how to make multithreaded device models
using AioContext, since we are using it for the block layer and
virtio-blk dataplane.  Doing the same work twice, on two different
frameworks, doesn't seem like a very good idea.

Paolo

  parent reply	other threads:[~2013-03-13 10:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13  5:59 [Qemu-devel] [RFC PATCH 0/2] port network layer onto glib Liu Ping Fan
2013-03-13  5:59 ` [Qemu-devel] [RFC PATCH 1/2] net: port tap " Liu Ping Fan
2013-03-13  5:59 ` [Qemu-devel] [RFC PATCH 2/2] net: port hub " Liu Ping Fan
2013-03-13 10:58 ` Paolo Bonzini [this message]
2013-03-13 12:34   ` [Qemu-devel] [RFC PATCH 0/2] port network layer " Anthony Liguori
2013-03-13 16:21     ` Paolo Bonzini
2013-03-13 17:06       ` mdroth
2013-03-13 17:31         ` Paolo Bonzini
2013-03-13 17:52           ` Michael S. Tsirkin
2013-03-13 18:09             ` Anthony Liguori
2013-03-13 17:23       ` Anthony Liguori
2013-03-13 17:35         ` Paolo Bonzini
2013-03-13 17:52           ` Anthony Liguori
2013-03-14  9:29             ` Stefan Hajnoczi
2013-03-14  9:53               ` Paolo Bonzini
2013-03-13 17:58           ` Anthony Liguori
2013-03-13 18:08             ` Paolo Bonzini
2013-03-13 18:51               ` Anthony Liguori
2013-03-14 10:04     ` Peter Maydell
2013-03-14 10:53       ` Paolo Bonzini
2013-03-14 11:00         ` Peter Maydell
2013-03-14 11:04           ` Paolo Bonzini
2013-03-14 11:26             ` Peter Maydell
2013-03-15  9:13       ` Stefan Hajnoczi
2013-03-19  9:30       ` Markus Armbruster
2013-03-19 10:12         ` Peter Maydell
2013-03-19 10:34           ` Paolo Bonzini
2013-03-19 10:38             ` Peter Maydell
2013-03-19 10:45               ` Paolo Bonzini
2013-03-14 14:08   ` liu ping fan
2013-03-14 14:18     ` Paolo Bonzini

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=51405BEA.6080109@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemulist@gmail.com \
    --cc=stefanha@gmail.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).