From: "Štefan Gula" <steweg@ynet.sk>
To: David Miller <davem@davemloft.net>
Cc: 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: Mon, 23 Jan 2012 23:23:43 +0100 [thread overview]
Message-ID: <CAGsizzJnQ6b6eSC0ZnAtFguU7_xDfWFPSY6L4DWXc24F+Ts2XQ@mail.gmail.com> (raw)
In-Reply-To: <20120123.134352.1621146585245670953.davem@davemloft.net>
2012/1/23 David Miller <davem@davemloft.net>:
> From: Eric Dumazet <eric.dumazet@gmail.com>
> Date: Mon, 23 Jan 2012 15:13:19 +0100
>
>> Le lundi 23 janvier 2012 à 14:12 +0100, Štefan Gula a écrit :
>>
>>> is there anything else needed from my side to get this code into the
>>> kernel or should I only wait for the maintainers to check it?
>>
>> net-next is/was not yet opened, you shall wait for the good time frame.
>>
>> Dont copy/paste a big message only to add one sentence at its end, its
>> really a waste of time for many of us.
>
> Also you were told of other ways to achieve the things you want to do,
> and I haven't seen any reasonable response that supports still adding
> this new code.
I am sorry about the mistakes I did (still new to kernel submitting
processes). I believe that I also explain to everybody who says
something similar that it is not entirely true and probably never will
be as none of the current SW allows you to create L2 Ethernet
Multipoint VPN solution in such simple way as almost all requires to
run special kind of software in user-space to provide control-plane
for such feature to work. This software must be able to run on various
platforms/architectures which makes it sometimes problematic. My
solution doesn't need this at all and extends the capability of gretap
interfaces in proper manner to be aligned with other forwarding
engines of gretap interfaces. I already have at least one successful
test done in other environment other than my own. So I assume some
people like this approach better than other solutions. For them and
also for myself, I believe it should be added.
next prev parent reply other threads:[~2012-01-23 22:24 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 [this message]
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
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=CAGsizzJnQ6b6eSC0ZnAtFguU7_xDfWFPSY6L4DWXc24F+Ts2XQ@mail.gmail.com \
--to=steweg@ynet.sk \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).