public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "Harout Hedeshian" <harouth@codeaurora.org>
To: <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>
Subject: TCP: Support configurable delayed-ack parameters
Date: Fri, 28 Feb 2014 08:14:22 -0700	[thread overview]
Message-ID: <00e801cf3497$c37255f0$4a5701d0$@codeaurora.org> (raw)

Hello David,

I found a thread from June 2012 (subject matches this email) discussing the
addition of parameters to manually tune the delayed TCP ACK parameters, and
add new TCP socket options for application specific tuning. The patch in
question would multiply the receive mss by some constant exposed in /proc.
We have experimented with a similar approach and found significant
improvements in performance when asymmetric links are utilized; specifically
where the hardware is limited in egress packets/sec (but not raw bandwidth).
As an example, in one test we saw a 100% improvement when doing rcv_mss*4.

You had responded to the original patch by stating that you are
fundamentally opposed to the feature. I'm trying to understand specifically
what your objections are. Checking tcp_measure_rcv_mss() current
implementation(as of 3.10),  I do not see any way for rcv_mss to grow beyond
the largest received skb length. 

Thanks,
Harout

--
Harout Hedeshian

Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by
The Linux Foundation

             reply	other threads:[~2014-02-28 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 15:14 Harout Hedeshian [this message]
2014-02-28 15:49 ` TCP: Support configurable delayed-ack parameters Eric Dumazet
2014-02-28 16:37   ` Harout Hedeshian
2014-02-28 16:52     ` Eric Dumazet

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='00e801cf3497$c37255f0$4a5701d0$@codeaurora.org' \
    --to=harouth@codeaurora.org \
    --cc=davem@davemloft.net \
    --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