From: Jon Maloy <jon.maloy@ericsson.com>
To: davem@davemloft.net
Cc: Jon Maloy <jon.maloy@ericsson.com>,
netdev@vger.kernel.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
tipc-discussion@lists.sourceforge.net
Subject: [PATCH net-next 0/3] tipc: redesign socket-level flow control
Date: Mon, 2 May 2016 10:22:33 -0400 [thread overview]
Message-ID: <1462198956-30181-1-git-send-email-jon.maloy@ericsson.com> (raw)
The socket-level flow control in TIPC has long been due for a major
overhaul. This series fixes this.
Jon Maloy (3):
tipc: re-enable compensation for socket receive buffer double counting
tipc: propagate peer node capabilities to socket layer
tipc: redesign connection-level flow control
net/tipc/core.c | 8 ++-
net/tipc/msg.h | 14 +++++-
net/tipc/node.c | 21 +++++++-
net/tipc/node.h | 6 ++-
net/tipc/socket.c | 144 +++++++++++++++++++++++++++++++++++-------------------
net/tipc/socket.h | 17 +++++--
6 files changed, 145 insertions(+), 65 deletions(-)
--
1.9.1
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
next reply other threads:[~2016-05-02 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 14:22 Jon Maloy [this message]
2016-05-02 14:22 ` [PATCH net-next 1/3] tipc: re-enable compensation for socket receive buffer double counting Jon Maloy
2016-05-02 14:22 ` [PATCH net-next 2/3] tipc: propagate peer node capabilities to socket layer Jon Maloy
2016-05-02 14:22 ` [PATCH net-next 3/3] tipc: redesign connection-level flow control Jon Maloy
2016-05-03 19:51 ` [PATCH net-next 0/3] tipc: redesign socket-level " David Miller
-- strict thread matches above, loose matches on Subject: below --
2016-05-02 15:58 Jon Maloy
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=1462198956-30181-1-git-send-email-jon.maloy@ericsson.com \
--to=jon.maloy@ericsson.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tipc-discussion@lists.sourceforge.net \
/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).