From: David Howells <dhowells@redhat.com>
To: netdev@vger.kernel.org
Cc: dhowells@redhat.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/7] rxrpc: More fixes and adjustments
Date: Fri, 30 Sep 2016 22:40:11 +0100 [thread overview]
Message-ID: <147527161156.28826.2148784664652062075.stgit@warthog.procyon.org.uk> (raw)
This set of patches contains some more fixes and adjustments:
(1) Actually display the retransmission indication previously added to the
tx_data trace.
(2) Switch to Congestion Avoidance mode properly at cwnd==ssthresh rather
than relying on detection during an overshoot and correction.
(3) Reduce ssthresh to the peer's declared receive window.
(4) The offset field in rxrpc_skb_priv can be dispensed with and the error
field is no longer used. Get rid of them.
(5) Keep the call timeouts as ktimes rather than jiffies to make it easier
to deal with RTT-based timeout values in future. Rounding to jiffies
is still necessary when the system timer is set.
(6) Fix the call timer handling to avoid retriggering of expired timeout
actions.
The patches can be found here also:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-rewrite
Tagged thusly:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
rxrpc-rewrite-20160930
David
---
David Howells (7):
rxrpc: Actually display the tx_data trace retransmission note
rxrpc: Switch to Congestion Avoidance mode at cwnd==ssthresh
rxrpc: Reduce ssthresh to peer's receive window
rxrpc: The offset field in struct rxrpc_skb_priv is unnecessary
rxrpc: Remove error from struct rxrpc_skb_priv as it is unused
rxrpc: Keep the call timeouts as ktimes rather than jiffies
rxrpc: Fix the call timer handling
include/trace/events/rxrpc.h | 28 +++++++-------
net/rxrpc/ar-internal.h | 10 ++---
net/rxrpc/call_event.c | 87 +++++++++++++++++++++++++-----------------
net/rxrpc/call_object.c | 19 +++------
net/rxrpc/conn_event.c | 3 +
net/rxrpc/input.c | 34 +++++++++-------
net/rxrpc/local_event.c | 3 +
net/rxrpc/misc.c | 15 +++++--
net/rxrpc/recvmsg.c | 6 +--
net/rxrpc/rxkad.c | 9 +++-
net/rxrpc/sendmsg.c | 8 ++--
net/rxrpc/sysctl.c | 8 ++--
12 files changed, 125 insertions(+), 105 deletions(-)
next reply other threads:[~2016-09-30 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 21:40 David Howells [this message]
2016-09-30 21:40 ` [PATCH net-next 1/7] rxrpc: Actually display the tx_data trace retransmission note David Howells
2016-09-30 21:40 ` [PATCH net-next 2/7] rxrpc: Switch to Congestion Avoidance mode at cwnd==ssthresh David Howells
2016-09-30 21:40 ` [PATCH net-next 3/7] rxrpc: Reduce ssthresh to peer's receive window David Howells
2016-09-30 21:40 ` [PATCH net-next 4/7] rxrpc: The offset field in struct rxrpc_skb_priv is unnecessary David Howells
2016-09-30 21:40 ` [PATCH net-next 5/7] rxrpc: Remove error from struct rxrpc_skb_priv as it is unused David Howells
2016-09-30 21:40 ` [PATCH net-next 6/7] rxrpc: Keep the call timeouts as ktimes rather than jiffies David Howells
2016-09-30 21:41 ` [PATCH net-next 7/7] rxrpc: Fix the call timer handling David Howells
2016-10-03 6:02 ` [PATCH net-next 0/7] rxrpc: More fixes and adjustments David Miller
2016-10-04 16:01 ` David Howells
2016-10-05 0:10 ` 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=147527161156.28826.2148784664652062075.stgit@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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.