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: Re: [PATCH net-next 0/9] rxrpc: Preparation for slow-start algorithm
Date: Thu, 22 Sep 2016 09:10:26 +0100 [thread overview]
Message-ID: <12907.1474531826@warthog.procyon.org.uk> (raw)
In-Reply-To: <147450474784.14691.229861132515739820.stgit@warthog.procyon.org.uk>
I'm going to post a V2 for this. I've used a couple of 64-bit division
operators rather than calling the appropriate function (which is fine on
x86_64) and managed to transpose the last two patches (causing an undefined
symbol in one of them).
David
prev parent reply other threads:[~2016-09-22 8:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 0:39 [PATCH net-next 0/9] rxrpc: Preparation for slow-start algorithm David Howells
2016-09-22 0:39 ` [PATCH net-next 1/9] rxrpc: Don't store the rxrpc header in the Tx queue sk_buffs David Howells
2016-09-22 0:39 ` [PATCH net-next 2/9] rxrpc: Add re-sent Tx annotation David Howells
2016-09-22 0:39 ` [PATCH net-next 3/9] rxrpc: Add per-peer RTT tracker David Howells
2016-09-22 4:34 ` kbuild test robot
2016-09-22 4:56 ` kbuild test robot
2016-09-22 0:39 ` [PATCH net-next 4/9] rxrpc: Send pings to get RTT data David Howells
2016-09-22 0:39 ` [PATCH net-next 5/9] rxrpc: Expedite ping response transmission David Howells
2016-09-22 0:39 ` [PATCH net-next 6/9] rxrpc: Add ktime_sub_ms() David Howells
2016-09-22 0:39 ` [PATCH net-next 7/9] rxrpc: Obtain RTT data by requesting ACKs on DATA packets David Howells
2016-09-22 0:40 ` [PATCH net-next 8/9] rxrpc: Reduce the number of PING ACKs sent David Howells
2016-09-22 1:25 ` kbuild test robot
2016-09-22 0:40 ` [PATCH net-next 9/9] rxrpc: Reduce the number of ACK-Requests sent David Howells
2016-09-22 5:24 ` kbuild test robot
2016-09-22 8:10 ` David Howells [this message]
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=12907.1474531826@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox