search for: 4faa7ef

...forming > fragmentation. > > Is that a fair summary? > > If yes, we can make this a bit harder by mixing in some > data per input and/or output devices. > > For example, just to give you the idea: > > diff --git a/net/core/dev.c b/net/core/dev.c > index 683d493..4faa7ef 100644 > --- a/net/core/dev.c > +++ b/net/core/dev.c > @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) > trace_netif_receive_skb(skb); > > orig_dev = skb->dev; > + skb_shinfo(skb)->ip6_frag_id = skb->dev->ifindex...

...forming > fragmentation. > > Is that a fair summary? > > If yes, we can make this a bit harder by mixing in some > data per input and/or output devices. > > For example, just to give you the idea: > > diff --git a/net/core/dev.c b/net/core/dev.c > index 683d493..4faa7ef 100644 > --- a/net/core/dev.c > +++ b/net/core/dev.c > @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) > trace_netif_receive_skb(skb); > > orig_dev = skb->dev; > + skb_shinfo(skb)->ip6_frag_id = skb->dev->ifindex...

...gt;> > >> If yes, we can make this a bit harder by mixing in some > >> data per input and/or output devices. > >> > >> For example, just to give you the idea: > >> > >> diff --git a/net/core/dev.c b/net/core/dev.c > >> index 683d493..4faa7ef 100644 > >> --- a/net/core/dev.c > >> +++ b/net/core/dev.c > >> @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) > >> trace_netif_receive_skb(skb); > >> > >> orig_dev = skb->dev; > >&...

...gt;> > >> If yes, we can make this a bit harder by mixing in some > >> data per input and/or output devices. > >> > >> For example, just to give you the idea: > >> > >> diff --git a/net/core/dev.c b/net/core/dev.c > >> index 683d493..4faa7ef 100644 > >> --- a/net/core/dev.c > >> +++ b/net/core/dev.c > >> @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) > >> trace_netif_receive_skb(skb); > >> > >> orig_dev = skb->dev; > >&...

...gt; > > If yes, we can make this a bit harder by mixing in some > > > data per input and/or output devices. > > > > > > For example, just to give you the idea: > > > > > > diff --git a/net/core/dev.c b/net/core/dev.c > > > index 683d493..4faa7ef 100644 > > > --- a/net/core/dev.c > > > +++ b/net/core/dev.c > > > @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) > > > trace_netif_receive_skb(skb); > > > > > > orig_dev = skb->dev; >...

...gt; > > If yes, we can make this a bit harder by mixing in some > > > data per input and/or output devices. > > > > > > For example, just to give you the idea: > > > > > > diff --git a/net/core/dev.c b/net/core/dev.c > > > index 683d493..4faa7ef 100644 > > > --- a/net/core/dev.c > > > +++ b/net/core/dev.c > > > @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) > > > trace_netif_receive_skb(skb); > > > > > > orig_dev = skb->dev; >...

...required is that two paths go through the same box performing fragmentation. Is that a fair summary? If yes, we can make this a bit harder by mixing in some data per input and/or output devices. For example, just to give you the idea: diff --git a/net/core/dev.c b/net/core/dev.c index 683d493..4faa7ef 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) trace_netif_receive_skb(skb); orig_dev = skb->dev; + skb_shinfo(skb)->ip6_frag_id = skb->dev->ifindex; skb_reset_network_header(skb)...

...required is that two paths go through the same box performing fragmentation. Is that a fair summary? If yes, we can make this a bit harder by mixing in some data per input and/or output devices. For example, just to give you the idea: diff --git a/net/core/dev.c b/net/core/dev.c index 683d493..4faa7ef 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) trace_netif_receive_skb(skb); orig_dev = skb->dev; + skb_shinfo(skb)->ip6_frag_id = skb->dev->ifindex; skb_reset_network_header(skb)...

Hello, On Di, 2015-01-27 at 18:08 +0200, Michael S. Tsirkin wrote: > On Tue, Jan 27, 2015 at 05:02:31PM +0100, Hannes Frederic Sowa wrote: > > On Di, 2015-01-27 at 09:26 -0500, Vlad Yasevich wrote: > > > On 01/27/2015 08:47 AM, Hannes Frederic Sowa wrote: > > > > On Di, 2015-01-27 at 10:42 +0200, Michael S. Tsirkin wrote: > > > >> On Tue, Jan 27, 2015

Hello, On Di, 2015-01-27 at 18:08 +0200, Michael S. Tsirkin wrote: > On Tue, Jan 27, 2015 at 05:02:31PM +0100, Hannes Frederic Sowa wrote: > > On Di, 2015-01-27 at 09:26 -0500, Vlad Yasevich wrote: > > > On 01/27/2015 08:47 AM, Hannes Frederic Sowa wrote: > > > > On Di, 2015-01-27 at 10:42 +0200, Michael S. Tsirkin wrote: > > > >> On Tue, Jan 27, 2015

...>> Is that a fair summary? >> >> If yes, we can make this a bit harder by mixing in some >> data per input and/or output devices. >> >> For example, just to give you the idea: >> >> diff --git a/net/core/dev.c b/net/core/dev.c >> index 683d493..4faa7ef 100644 >> --- a/net/core/dev.c >> +++ b/net/core/dev.c >> @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) >> trace_netif_receive_skb(skb); >> >> orig_dev = skb->dev; >> + skb_shinfo(skb)->ip6_frag_...

...>> Is that a fair summary? >> >> If yes, we can make this a bit harder by mixing in some >> data per input and/or output devices. >> >> For example, just to give you the idea: >> >> diff --git a/net/core/dev.c b/net/core/dev.c >> index 683d493..4faa7ef 100644 >> --- a/net/core/dev.c >> +++ b/net/core/dev.c >> @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) >> trace_netif_receive_skb(skb); >> >> orig_dev = skb->dev; >> + skb_shinfo(skb)->ip6_frag_...

...s that a fair summary? > > > > If yes, we can make this a bit harder by mixing in some > > data per input and/or output devices. > > > > For example, just to give you the idea: > > > > diff --git a/net/core/dev.c b/net/core/dev.c > > index 683d493..4faa7ef 100644 > > --- a/net/core/dev.c > > +++ b/net/core/dev.c > > @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) > > trace_netif_receive_skb(skb); > > > > orig_dev = skb->dev; > > + skb_shinfo(skb)->ip...

...s that a fair summary? > > > > If yes, we can make this a bit harder by mixing in some > > data per input and/or output devices. > > > > For example, just to give you the idea: > > > > diff --git a/net/core/dev.c b/net/core/dev.c > > index 683d493..4faa7ef 100644 > > --- a/net/core/dev.c > > +++ b/net/core/dev.c > > @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) > > trace_netif_receive_skb(skb); > > > > orig_dev = skb->dev; > > + skb_shinfo(skb)->ip...

...a fair summary? No answer here? > > If yes, we can make this a bit harder by mixing in some > > data per input and/or output devices. > > > > For example, just to give you the idea: > > > > diff --git a/net/core/dev.c b/net/core/dev.c > > index 683d493..4faa7ef 100644 > > --- a/net/core/dev.c > > +++ b/net/core/dev.c > > @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) > > trace_netif_receive_skb(skb); > > > > orig_dev = skb->dev; > > + skb_shinfo(skb)->ip...

...a fair summary? No answer here? > > If yes, we can make this a bit harder by mixing in some > > data per input and/or output devices. > > > > For example, just to give you the idea: > > > > diff --git a/net/core/dev.c b/net/core/dev.c > > index 683d493..4faa7ef 100644 > > --- a/net/core/dev.c > > +++ b/net/core/dev.c > > @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) > > trace_netif_receive_skb(skb); > > > > orig_dev = skb->dev; > > + skb_shinfo(skb)->ip...

...gt; If yes, we can make this a bit harder by mixing in some >>>> data per input and/or output devices. >>>> >>>> For example, just to give you the idea: >>>> >>>> diff --git a/net/core/dev.c b/net/core/dev.c >>>> index 683d493..4faa7ef 100644 >>>> --- a/net/core/dev.c >>>> +++ b/net/core/dev.c >>>> @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) >>>> trace_netif_receive_skb(skb); >>>> >>>> orig_dev = skb-&...

...gt; If yes, we can make this a bit harder by mixing in some >>>> data per input and/or output devices. >>>> >>>> For example, just to give you the idea: >>>> >>>> diff --git a/net/core/dev.c b/net/core/dev.c >>>> index 683d493..4faa7ef 100644 >>>> --- a/net/core/dev.c >>>> +++ b/net/core/dev.c >>>> @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) >>>> trace_netif_receive_skb(skb); >>>> >>>> orig_dev = skb-&...

...ake this a bit harder by mixing in some > > > > data per input and/or output devices. > > > > > > > > For example, just to give you the idea: > > > > > > > > diff --git a/net/core/dev.c b/net/core/dev.c > > > > index 683d493..4faa7ef 100644 > > > > --- a/net/core/dev.c > > > > +++ b/net/core/dev.c > > > > @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) > > > > trace_netif_receive_skb(skb); > > > > > > > >...

...ake this a bit harder by mixing in some > > > > data per input and/or output devices. > > > > > > > > For example, just to give you the idea: > > > > > > > > diff --git a/net/core/dev.c b/net/core/dev.c > > > > index 683d493..4faa7ef 100644 > > > > --- a/net/core/dev.c > > > > +++ b/net/core/dev.c > > > > @@ -3625,6 +3625,7 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc) > > > > trace_netif_receive_skb(skb); > > > > > > > >...