On 06/18/15 at 09:49pm, Roopa Prabhu wrote:
> +static inline struct lwtunnel_state *lwtunnel_skb_lwstate(struct sk_buff
> *skb)
> +{
> + struct rtable *rt = (struct rtable *)skb_dst(skb);
> +
> + return rt->rt_lwtstate;
> +}
Noticed while rebasing onto your patches. This needs an
ifdef CO
On 6/21/15, 1:40 PM, Thomas Graf wrote:
On 06/20/15 at 07:27am, roopa wrote:
On 6/19/15, 11:39 AM, Robert Shearman wrote:
Sorry for not being clear, but I meant that there would have to be
lwtunnel_skb_lwstate functions for ipv4 and ipv6 to match the output
functions. So in the vxlan use case
On 6/21/15, 1:32 PM, Thomas Graf wrote:
On 06/18/15 at 09:49pm, Roopa Prabhu wrote:
+#include
+#include
+
+#define LWTUNNEL_HASH_BITS 7
+#define LWTUNNEL_HASH_SIZE (1 << LWTUNNEL_HASH_BITS)
+
+struct lwtunnel_hdr {
+ int len;
+ __u8data[0];
+};
The name
On 6/20/15, 9:38 AM, Nikolay Aleksandrov wrote:
<<>>
diff --git a/net/core/lwtunnel.c b/net/core/lwtunnel.c
new file mode 100644
index 000..29c7802
--- /dev/null
+++ b/net/core/lwtunnel.c
@@ -0,0 +1,162 @@
+/*
+ * lwtunnelInfrastructure for light weight tunnels like mpls
+ *
+ *
+ *
On 06/20/15 at 07:27am, roopa wrote:
> On 6/19/15, 11:39 AM, Robert Shearman wrote:
> >On 19/06/15 19:34, roopa wrote:
> >>On 6/19/15, 10:25 AM, Robert Shearman wrote:
> >>>n 19/06/15 16:14, roopa wrote:
> >>>
> >>In the netdevice case, this output function is not called atall. It
> >>should just f
On 06/18/15 at 09:49pm, Roopa Prabhu wrote:
> +#include
> +#include
> +
> +#define LWTUNNEL_HASH_BITS 7
> +#define LWTUNNEL_HASH_SIZE (1 << LWTUNNEL_HASH_BITS)
> +
> +struct lwtunnel_hdr {
> + int len;
> + __u8data[0];
> +};
The name header is a bit misleading
<<>>
> diff --git a/net/core/lwtunnel.c b/net/core/lwtunnel.c
> new file mode 100644
> index 000..29c7802
> --- /dev/null
> +++ b/net/core/lwtunnel.c
> @@ -0,0 +1,162 @@
> +/*
> + * lwtunnel Infrastructure for light weight tunnels like mpls
> + *
> + *
> + * This program is free sof
On 6/19/15, 11:39 AM, Robert Shearman wrote:
On 19/06/15 19:34, roopa wrote:
On 6/19/15, 10:25 AM, Robert Shearman wrote:
n 19/06/15 16:14, roopa wrote:
In the netdevice case, this output function is not called atall. It
should just follow the existing netdevice the route is pointing to.
So
On 19/06/15 19:34, roopa wrote:
On 6/19/15, 10:25 AM, Robert Shearman wrote:
n 19/06/15 16:14, roopa wrote:
Today lwtunnel_skb_lwstate is called from lwtunnel_output which is only
called from ipv4 code.
And my ipv6 variant code was supposed to have a 6 suffix. something like
lwtunnel_output6.
O
On 6/19/15, 10:25 AM, Robert Shearman wrote:
n 19/06/15 16:14, roopa wrote:
Today lwtunnel_skb_lwstate is called from lwtunnel_output which is only
called from ipv4 code.
And my ipv6 variant code was supposed to have a 6 suffix. something like
lwtunnel_output6.
Or to be more explicit i will prob
n 19/06/15 16:14, roopa wrote:
On 6/19/15, 7:43 AM, Robert Shearman wrote:
+
+static inline struct lwtunnel_state *lwtunnel_skb_lwstate(struct
sk_buff *skb)
+{
+struct rtable *rt = (struct rtable *)skb_dst(skb);
+
+return rt->rt_lwtstate;
+}
It doesn't look like this patch will build
On 6/19/15, 7:43 AM, Robert Shearman wrote:
diff --git a/include/linux/lwtunnel.h b/include/linux/lwtunnel.h
new file mode 100644
+/* lw tunnel state flags */
+#define LWTUNNEL_STATE_OUTPUT_REDIRECT 0x1
+
+#define lwtunnel_output_redirect(lwtstate) (lwtstate && \
+(lwtstate->flags
On 19/06/15 05:49, Roopa Prabhu wrote:
From: Roopa Prabhu
provides ops to parse, build and output encaped
packets for drivers that want to attach tunnel encap
information to routes.
Signed-off-by: Roopa Prabhu
---
include/linux/lwtunnel.h |6 ++
include/net/lwtunnel.h| 8
From: Roopa Prabhu
provides ops to parse, build and output encaped
packets for drivers that want to attach tunnel encap
information to routes.
Signed-off-by: Roopa Prabhu
---
include/linux/lwtunnel.h |6 ++
include/net/lwtunnel.h| 84 +
include/uapi/linux
14 matches
Mail list logo
