From: David Miller <davem@davemloft.net>
To: steweg@ynet.sk
Cc: jesse@nicira.com, joseph.glanville@orionvm.com.au,
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 20:37:46 -0500 (EST) [thread overview]
Message-ID: <20120125.203746.1977019610549185259.davem@davemloft.net> (raw)
In-Reply-To: <CAGsizzJnRy74ni-HH=5q1VR4g6sfDPg9SFw4UKgSjJjkSR8OJA@mail.gmail.com>
From: Štefan Gula <steweg@ynet.sk>
Date: Wed, 25 Jan 2012 23:57:18 +0100
> The performance is one of the most critical thing why I have chosen to
> build kernel patch in the first place instead of some user-space app.
> If I used this approach, I would probably end up with patch for
> OpenVPN project instead in that time. I am not telling that
> openvswitch is not a good place for prototyping, but I believe that
> this patch is beyond that border as it successfully run in environment
> with more 98 linux-based APs, used for 4K+ users, with no issue for
> more than 2 years. The performance results from Joseph Glanville even
> adds value to it. So I still don't get the point, why my patch and
> openvswitch cannot coexists in the kernel together and let user/admin
> to choose to correct solution for him/her.
You don't even know if openvswitch could provide acceptable levels
of performance, because you haven't even tried.
I'm not applying your patch.
next prev parent reply other threads:[~2012-01-26 1:37 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
2012-01-25 22:57 ` Štefan Gula
2012-01-25 23:18 ` Dave Taht
2012-01-26 1:37 ` David Miller [this message]
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.203746.1977019610549185259.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).