From: David Miller <davem@davemloft.net>
To: jon.maloy@ericsson.com
Cc: netdev@vger.kernel.org, viro@zeniv.linux.org.uk,
parthasarathy.bhuvaragan@ericsson.com, ying.xue@windriver.com,
maloy@donjonn.com, tipc-discussion@lists.sourceforge.net
Subject: Re: [net-next 0/3] tipc: improve interaction socket-link
Date: Mon, 16 Jan 2017 14:45:14 -0500 (EST) [thread overview]
Message-ID: <20170116.144514.1071967219363714348.davem@davemloft.net> (raw)
In-Reply-To: <1483457208-29033-1-git-send-email-jon.maloy@ericsson.com>
From: Jon Maloy <jon.maloy@ericsson.com>
Date: Tue, 3 Jan 2017 10:26:45 -0500
> 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.
This doesn't apply to net-next, also the Date in your emails is 10 days
in the past. What's going on here?
next prev parent reply other threads:[~2017-01-16 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 15:26 [net-next 0/3] tipc: improve interaction socket-link Jon Maloy
2017-01-03 15:26 ` [net-next 1/3] tipc: unify tipc_wait_for_sndpkt() and tipc_wait_for_sndmsg() functions Jon Maloy
2017-01-03 15:26 ` [net-next 2/3] tipc: modify struct tipc_plist to be more versatile Jon Maloy
2017-01-03 15:26 ` [net-next 3/3] tipc: reduce risk of user starvation during link congestion Jon Maloy
2017-01-16 19:45 ` David Miller [this message]
2017-01-16 20:35 ` [net-next 0/3] tipc: improve interaction socket-link Jon Maloy
2017-01-16 21:54 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2017-01-03 15:55 Jon Maloy
2017-01-03 16:13 ` 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=20170116.144514.1071967219363714348.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=maloy@donjonn.com \
--cc=netdev@vger.kernel.org \
--cc=parthasarathy.bhuvaragan@ericsson.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
--cc=ying.xue@windriver.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 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).