From: Stephen Hemminger <shemminger@vyatta.com>
To: David Miller <davem@davemloft.net>
Cc: eric.dumazet@gmail.com, bhutchings@solarflare.com,
netdev@vger.kernel.org
Subject: Re: [PATCH v2] ipv4: Early TCP socket demux.
Date: Wed, 20 Jun 2012 14:04:54 -0700 [thread overview]
Message-ID: <20120620140454.36847c65@s6510.linuxnetplumber.net> (raw)
In-Reply-To: <20120620.140121.1603737472432326278.davem@davemloft.net>
On Wed, 20 Jun 2012 14:01:21 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: Eric Dumazet <eric.dumazet@gmail.com>
> Date: Wed, 20 Jun 2012 20:40:04 +0200
>
> > If someone wants to tune its linux router, he probably already disables
> > GRO because of various issues with too big packets.
> >
> > GRO adds a significant cost to forwarding path.
>
> No, Ben is right Eric. GRO decreases the costs, because it means we
> only need to make one forwarding/netfilter/classification decision for
> N packets instead of 1.
GRO is also important for routers that interact with VM's.
It helps reduce the per-packet wakeup of the guest VM's.
next prev parent reply other threads:[~2012-06-20 21:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 23:39 [PATCH v2] ipv4: Early TCP socket demux David Miller
2012-06-20 0:21 ` Ben Hutchings
2012-06-20 0:54 ` David Miller
2012-06-20 1:03 ` Ben Hutchings
2012-06-20 1:05 ` David Miller
2012-06-20 2:02 ` David Miller
2012-06-20 18:16 ` Ben Hutchings
2012-06-20 2:35 ` Stephen Hemminger
2012-06-20 4:46 ` David Miller
2012-06-20 5:49 ` Eric Dumazet
2012-06-20 5:51 ` Eric Dumazet
2012-06-20 6:14 ` David Miller
2012-06-20 16:21 ` Rick Jones
2012-06-20 5:59 ` Eric Dumazet
2012-06-20 6:14 ` David Miller
2012-06-20 10:15 ` David Miller
2012-06-20 11:03 ` Eric Dumazet
2012-06-20 11:09 ` David Miller
2012-06-20 12:38 ` Eric Dumazet
2012-06-20 22:29 ` David Miller
2012-06-20 18:07 ` Ben Hutchings
2012-06-20 18:40 ` Eric Dumazet
2012-06-20 21:01 ` David Miller
2012-06-20 21:04 ` Stephen Hemminger [this message]
2012-06-20 21:17 ` Eric Dumazet
2012-06-20 21:26 ` David Miller
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=20120620140454.36847c65@s6510.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=bhutchings@solarflare.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.