From: Or Gerlitz <ogerlitz@Voltaire.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH RFC] tun: export underlying socket
Date: Tue, 15 Sep 2009 16:02:35 +0300 [thread overview]
Message-ID: <4AAF906B.4040608@Voltaire.com> (raw)
In-Reply-To: <20090914150313.GA18560@gondor.apana.org.au>
Herbert Xu wrote:
> TSO is not a problem because we provide a software fallback when
> the hardware does not support it. So guests should always enable
> TSO if they support it and not worry about the physical NIC.
Yes, I am aware that GSO can take action and so software segmentation is / can be done when the HW isn't capable of doing so (and I assume the same can go for checksum). I assume that by "we provide" you mean the core networking code, correct? in what level? I assume its not the TCP one, since this is not applicable a tun/bridge scheme. Simper example would be the vm nic MTU... with vhost attached directly to a nic with packet socket you can learn/control it all, where when tun/bridge is used, how can you tell?
Or.
next prev parent reply other threads:[~2009-09-15 13:02 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 [this message]
2009-09-15 13:31 ` Herbert Xu
2009-09-14 15:40 ` Michael S. Tsirkin
2009-09-15 13:11 ` Or Gerlitz
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=4AAF906B.4040608@Voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.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.