From: Jon Maloy <jon.maloy@ericsson.com>
To: davem@davemloft.net
Cc: Jon Maloy <jon.maloy@ericsson.com>,
netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net
Subject: [net-next 0/3] tipc: improve interaction socket-link
Date: Tue, 3 Jan 2017 10:55:08 -0500 [thread overview]
Message-ID: <1483458911-32549-1-git-send-email-jon.maloy@ericsson.com> (raw)
We fix a very real starvation problem that may occur when a link
encounters send buffer congestion. At the same time we make the
interaction between the socket and link layer simpler and more
consistent.
Jon Maloy (3):
tipc: unify tipc_wait_for_sndpkt() and tipc_wait_for_sndmsg()
functions
tipc: modify struct tipc_plist to be more versatile
tipc: reduce risk of user starvation during link congestion
net/tipc/bcast.c | 6 +-
net/tipc/link.c | 75 ++++-----
net/tipc/msg.h | 2 -
net/tipc/name_table.c | 100 +++++++----
net/tipc/name_table.h | 21 +--
net/tipc/node.c | 15 +-
net/tipc/socket.c | 449 ++++++++++++++++++++++----------------------------
7 files changed, 319 insertions(+), 349 deletions(-)
--
2.7.4
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
next reply other threads:[~2017-01-03 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 15:55 Jon Maloy [this message]
2017-01-03 15:55 ` [net-next 1/3] tipc: unify tipc_wait_for_sndpkt() and tipc_wait_for_sndmsg() functions Jon Maloy
2017-01-03 15:55 ` [net-next 2/3] tipc: modify struct tipc_plist to be more versatile Jon Maloy
2017-01-03 15:55 ` [net-next 3/3] tipc: reduce risk of user starvation during link congestion Jon Maloy
2017-01-03 16:13 ` [net-next 0/3] tipc: improve interaction socket-link David Miller
-- strict thread matches above, loose matches on Subject: below --
2017-01-03 15:26 Jon Maloy
2017-01-16 19:45 ` David Miller
2017-01-16 20:35 ` Jon Maloy
2017-01-16 21:54 ` 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=1483458911-32549-1-git-send-email-jon.maloy@ericsson.com \
--to=jon.maloy@ericsson.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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).