From: Yuchung Cheng <ycheng@google.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, brakmo@fb.com, ncardwell@google.com,
ysseung@google.com, edumazet@google.com,
Yuchung Cheng <ycheng@google.com>
Subject: [PATCH net 0/2] fix DCTCP delayed ACK
Date: Thu, 12 Jul 2018 06:04:51 -0700 [thread overview]
Message-ID: <20180712130453.95007-1-ycheng@google.com> (raw)
This patch series addresses the issue that sometimes DCTCP
fail to acknowledge the latest sequence and result in sender timeout
if inflight is small.
Yuchung Cheng (2):
tcp: fix dctcp delayed ACK schedule
tcp: remove DELAYED ACK events in DCTCP
include/net/tcp.h | 2 --
net/ipv4/tcp_dctcp.c | 31 ++++---------------------------
net/ipv4/tcp_output.c | 4 ----
3 files changed, 4 insertions(+), 33 deletions(-)
--
2.18.0.203.gfac676dfb9-goog
next reply other threads:[~2018-07-12 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 13:04 Yuchung Cheng [this message]
2018-07-12 13:04 ` [PATCH net 1/2] tcp: fix dctcp delayed ACK schedule Yuchung Cheng
2018-07-12 13:09 ` Lawrence Brakmo
2018-07-12 13:04 ` [PATCH net 2/2] tcp: remove DELAYED ACK events in DCTCP Yuchung Cheng
2018-07-12 13:09 ` Lawrence Brakmo
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=20180712130453.95007-1-ycheng@google.com \
--to=ycheng@google.com \
--cc=brakmo@fb.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ysseung@google.com \
/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.