netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fan Du <fan.du@intel.com>
To: johnwheffner@gmail.com
Cc: davem@davemloft.net, netdev@vger.kernel.org, fengyuleidian0615@gmail.com
Subject: [PATCH net-next 0/4] Fix for TCP PMTU
Date: Tue, 10 Mar 2015 17:16:22 +0800	[thread overview]
Message-ID: <1425978986-8512-1-git-send-email-fan.du@intel.com> (raw)

Hi,

This patchset performs some minor fixes for TCP PMTU,
including correct length condition checking when building
probe segment, then checking if there is enough data avaiable
with probe_size, and finally a cosmetics patch to rename
tcp_mtu_probing with tcp_blackhole_probe for clarity.
In addition, clamp sysctl_tcp_probe_threshold.

Fan Du (4):
  ipv4: Rename tcp_mtu_probing to tcp_blackhole_probe
  ipv4: Correct two conditions checking when buildig nskb
  ipv4: Use probe_size to check write queue data length
  ipv4: clamp sysctl_tcp_probe_threshold

 net/ipv4/tcp_output.c |   14 ++++++--------
 net/ipv4/tcp_timer.c  |    5 +++--
 2 files changed, 9 insertions(+), 10 deletions(-)

             reply	other threads:[~2015-03-10  9:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10  9:16 Fan Du [this message]
2015-03-10  9:16 ` [PATCH net-next 1/4] ipv4: Rename tcp_mtu_probing to tcp_blackhole_probe Fan Du
2015-03-10  9:16 ` [PATCH net-next 2/4] ipv4: Correct two conditions checking when buildig nskb Fan Du
2015-03-18 12:44   ` John Heffner
2015-03-10  9:16 ` [PATCH net-next 3/4] ipv4: Use probe_size to check write queue data length Fan Du
2015-03-10 12:26   ` John Heffner
2015-03-18  1:37     ` Fan Du
2015-03-18 12:41       ` John Heffner
2015-03-10  9:16 ` [PATCH net-next 4/4] ipv4: clamp sysctl_tcp_probe_threshold Fan Du

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=1425978986-8512-1-git-send-email-fan.du@intel.com \
    --to=fan.du@intel.com \
    --cc=davem@davemloft.net \
    --cc=fengyuleidian0615@gmail.com \
    --cc=johnwheffner@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).