From: David Miller <davem@davemloft.net>
To: jesse@nicira.com
Cc: joseph.glanville@orionvm.com.au, steweg@ynet.sk,
eric.dumazet@gmail.com, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch v4, kernel version 3.2.1] net/ipv4/ip_gre: Ethernet multipoint GRE over IP
Date: Wed, 25 Jan 2012 16:55:48 -0500 (EST) [thread overview]
Message-ID: <20120125.165548.596418893115900979.davem@davemloft.net> (raw)
In-Reply-To: <CAEP_g=9H9dV9=qtFPh4YeTNQ-t+UZGw-YqZ6hFWVNXjFy+GCZg@mail.gmail.com>
From: Jesse Gross <jesse@nicira.com>
Date: Tue, 24 Jan 2012 23:11:06 -0800
> On Tue, Jan 24, 2012 at 8:02 PM, David Miller <davem@davemloft.net> wrote:
>> From: Joseph Glanville <joseph.glanville@orionvm.com.au>
>> Date: Wed, 25 Jan 2012 14:48:37 +1100
>>
>>> The reason why this patch is useful is that it stands to be the only
>>> true mulitpoint L2 VPN with a kernel space forwarding plane.
>>
>> So what you're telling me is that I added this huge openvswitch
>> thing essentially for nothing?
>
> I think it's actually the opposite - Open vSwitch can be used to
> implement this type of thing as well as for many other use cases.
Then openvswitch is exactly where you should be prototyping and
implementing support for this sort of stuff.
And only if you cannot obtain reasonable performance using openvswitch
should you be even entertaining the notion of a static implementation.
That's the whole premise behind putting openvswitch into the tree, so
that guys like you can play around in userspace without having to make
any kernel changes at all.
I am not applying these patches, the more things you say the more I am
convinced they are not appropriate.
next prev parent reply other threads:[~2012-01-25 21:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18947389.2811326843064500.JavaMail.root@5-MeO-DMT.ynet.sk>
2012-01-17 23:33 ` [patch v4, kernel version 3.2.1] net/ipv4/ip_gre: Ethernet multipoint GRE over IP Stefan Gula
2012-01-23 13:12 ` Štefan Gula
2012-01-23 14:13 ` Eric Dumazet
2012-01-23 18:43 ` David Miller
2012-01-23 22:23 ` Štefan Gula
2012-01-25 3:48 ` Joseph Glanville
2012-01-25 4:02 ` David Miller
2012-01-25 7:11 ` Jesse Gross
2012-01-25 7:38 ` Štefan Gula
2012-01-25 8:37 ` Eric Dumazet
2012-01-25 9:17 ` Štefan Gula
2012-01-25 15:25 ` Joseph Glanville
2012-01-25 21:55 ` David Miller [this message]
2012-01-25 22:57 ` Štefan Gula
2012-01-25 23:18 ` Dave Taht
2012-01-26 1:37 ` David Miller
2012-01-26 10:57 ` Štefan Gula
2012-01-26 18:30 ` David Miller
2012-01-26 22:24 ` Joseph Glanville
2012-01-27 5:59 ` Eric Dumazet
2012-01-27 10:54 ` Joseph Glanville
2012-01-27 21:55 ` Jesse Gross
2012-01-27 21:50 ` Jesse Gross
2012-01-25 5:53 ` Eric Dumazet
2012-01-25 16:57 ` Stephen Hemminger
2012-01-25 21:01 ` Štefan Gula
2012-01-25 21:49 ` David Miller
2012-01-25 22:30 ` Štefan Gula
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=20120125.165548.596418893115900979.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jesse@nicira.com \
--cc=jmorris@namei.org \
--cc=joseph.glanville@orionvm.com.au \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steweg@ynet.sk \
--cc=yoshfuji@linux-ipv6.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 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).