[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1383884683.9412.174.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Thu, 07 Nov 2013 20:24:43 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: David Miller <davem@...emloft.net>, bhutchings@...arflare.com,
christoph.paasch@...ouvain.be, netdev@...r.kernel.org,
hkchu@...gle.com, mwdalton@...gle.com
Subject: Re: [PATCH v4 net-next] net: introduce dev_set_forwarding()
On Fri, 2013-11-08 at 12:10 +0800, Herbert Xu wrote:
> Well you still don't seem to be getting this: If you need it for
> the host then you will need it even more for virt because the
> network stack there is much longer.
>
> So having it only available to the host without also giving it
> to virt makes *zero* sense.
I am fine with this, but how can we know the packet is going to be
delivered to virt instead of forwarded to ethernet ?
Do we want the equivalent of 'IP early demux', done at GRO layer ? ;)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists