From: David Miller <davem@davemloft.net>
To: alexandre.sidorenko@hpe.com
Cc: netdev@vger.kernel.org
Subject: Re: Receive offloads, small RCVBUF and zero TCP window
Date: Mon, 28 Nov 2016 15:54:59 -0500 (EST) [thread overview]
Message-ID: <20161128.155459.1527519991492144879.davem@davemloft.net> (raw)
In-Reply-To: <2080597.A38JFJZ1AD@zbook>
From: Alex Sidorenko <alexandre.sidorenko@hpe.com>
Date: Mon, 28 Nov 2016 15:49:26 -0500
> Now the question is whether is is OK to have icsk->icsk_ack.rcv_mss
> larger than MTU.
It absolutely is not OK.
If VMWare wants to receive large frames for batching purposes it must
use GRO or similar to achieve that, not just send vanilla frames into
the stack which are larger than the device MTU.
next prev parent reply other threads:[~2016-11-28 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 20:49 Receive offloads, small RCVBUF and zero TCP window Alex Sidorenko
2016-11-28 20:54 ` David Miller [this message]
2016-11-28 21:14 ` Alex Sidorenko
2016-11-30 15:10 ` Alex Sidorenko
2016-11-28 22:01 ` Marcelo Ricardo Leitner
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=20161128.155459.1527519991492144879.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexandre.sidorenko@hpe.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).