From: Or Gerlitz <or.gerlitz@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Or Gerlitz <ogerlitz@voltaire.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH RFC] tun: export underlying socket
Date: Tue, 15 Sep 2009 16:11:22 +0300 [thread overview]
Message-ID: <15ddcffd0909150611s2e172f19xa8abe794abf13159@mail.gmail.com> (raw)
In-Reply-To: <20090914154011.GB3556@redhat.com>
On 9/14/09, Michael S. Tsirkin <mst@redhat.com> wrote:
>> 3. for tun fd
>> VM.TX is translated by vhost to sendmsg which is translated by tun to
>> netif_rx which is then handled by the bridge
>> NIC RX goes to the bridge which xmits the packet a tun interface, now
>> what makes tun provide this packet to vhost and how it is done?
> Same as above. vhost polls tun and calls recvmsg on the socket
no, correct if I'm wrong, but recvmsg calls tun_do_read and the later
calls tun_put_user to the packet goes to user space and not into the virtq
Or.
next prev parent reply other threads:[~2009-09-15 13:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 12:59 [PATCH RFC] tun: export underlying socket Michael S. Tsirkin
2009-09-10 13:19 ` Eric Dumazet
2009-09-10 13:27 ` Michael S. Tsirkin
2009-09-11 4:17 ` Paul Moore
2009-09-11 4:59 ` Michael S. Tsirkin
2009-09-11 5:36 ` Michael S. Tsirkin
2009-09-11 6:10 ` Eric Dumazet
2009-09-11 9:44 ` Michael S. Tsirkin
2009-09-14 8:01 ` Or Gerlitz
2009-09-14 8:07 ` Or Gerlitz
2009-09-14 8:09 ` Michael S. Tsirkin
2009-09-14 8:17 ` Or Gerlitz
2009-09-14 9:11 ` Michael S. Tsirkin
2009-09-14 9:43 ` Or Gerlitz
2009-09-14 10:10 ` Michael S. Tsirkin
2009-09-14 14:06 ` Or Gerlitz
2009-09-14 15:03 ` Herbert Xu
2009-09-15 13:02 ` Or Gerlitz
2009-09-15 13:31 ` Herbert Xu
2009-09-14 15:40 ` Michael S. Tsirkin
2009-09-15 13:11 ` Or Gerlitz [this message]
2009-09-15 13:18 ` Michael S. Tsirkin
2009-11-02 17:20 ` [PATCHv2] " Michael S. Tsirkin
2009-11-03 15:10 ` Herbert Xu
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=15ddcffd0909150611s2e172f19xa8abe794abf13159@mail.gmail.com \
--to=or.gerlitz@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@voltaire.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).