From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next] ifb: support more features
Date: Mon, 09 May 2016 00:01:54 -0400 (EDT) [thread overview]
Message-ID: <20160509.000154.2249776807369776317.davem@davemloft.net> (raw)
In-Reply-To: <1462583999.13075.67.camel@edumazet-glaptop3.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 06 May 2016 18:19:59 -0700
> From: Eric Dumazet <edumazet@google.com>
>
> When using ifb+netem on ingress on SIT/IPIP/GRE traffic,
> GRO packets are not properly processed.
>
> Segmentation should not be forced, since ifb is already adding
> quite a performance hit.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Applied.
prev parent reply other threads:[~2016-05-09 4:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 23:41 [PATCH net-next] ifb: support more features Eric Dumazet
2016-05-07 0:21 ` Eric Dumazet
2016-05-07 1:19 ` [PATCH v2 " Eric Dumazet
2016-05-08 5:41 ` Eric Dumazet
2016-05-08 16:08 ` Eric Dumazet
2016-05-08 17:35 ` Eric Dumazet
2016-05-09 17:22 ` Alexander Duyck
2016-05-09 17:39 ` Eric Dumazet
2016-05-09 17:41 ` Eric Dumazet
2016-05-09 4:01 ` David Miller [this message]
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=20160509.000154.2249776807369776317.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.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).