From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jesse Gross <jesse@nicira.com>
Cc: David Miller <davem@davemloft.net>,
joseph.glanville@orionvm.com.au, steweg@ynet.sk,
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 09:37:04 +0100 [thread overview]
Message-ID: <1327480624.14373.51.camel@edumazet-laptop> (raw)
In-Reply-To: <CAEP_g=9H9dV9=qtFPh4YeTNQ-t+UZGw-YqZ6hFWVNXjFy+GCZg@mail.gmail.com>
Le mardi 24 janvier 2012 à 23:11 -0800, Jesse Gross a écrit :
> 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. On
> the other hand, even when implementing a multipoint L2 solution it can
> be useful to have additional levels of control but you can't do that
> with this patch because it essentially statically glues together
> tunneling and bridging.
Unless you can provide a working solution in a very short time, this
patch is a pragmatic one.
Code is not perfect and could be improved (for example using a helper
function to keep ipgre_rcv() shorter and reduce indentation level)
Stefan, could you move this code out of ipgre_rcv() ?
+#ifdef CONFIG_NET_IPGRE_BRIDGE
+ if (ipv4_is_multicast(tunnel->parms.iph.daddr)) {
+ tethhdr = eth_hdr(skb);
+ if (!is_multicast_ether_addr(
+ tethhdr->h_source)) {
+ head = &tunnel->hash[
+ ipgre_tap_bridge_hash(
+ tethhdr->h_source)];
+ entry = ipgre_tap_bridge_find_rcu(head,
+ tethhdr->h_source);
+ if (likely(entry)) {
+ entry->raddr = orig_source;
+ entry->updated = jiffies;
+ } else {
+ spin_lock(&tunnel->hash_lock);
+ if (!ipgre_tap_bridge_find(head,
+ tethhdr->h_source))
+ ipgre_tap_bridge_create(
+ head,
+ orig_source,
+ tethhdr->h_source);
+ spin_unlock(&tunnel->hash_lock);
+ }
+ }
+ }
+#endif
next prev parent reply other threads:[~2012-01-25 8: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 [this message]
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=1327480624.14373.51.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--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).