netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Maloy <jon.maloy@ericsson.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: <mohan.krishna.ghanta.krishnamurthy@ericsson.com>,
	<tung.q.nguyen@dektech.com.au>, <hoang.h.le@dektech.com.au>,
	<jon.maloy@ericsson.com>, <canh.d.luu@dektech.com.au>,
	<ying.xue@windriver.com>, <tipc-discussion@lists.sourceforge.net>
Subject: [net-next 0/9] tipc: improvements to group messaging
Date: Mon, 8 Jan 2018 20:34:31 +0100	[thread overview]
Message-ID: <1515440080-27377-1-git-send-email-jon.maloy@ericsson.com> (raw)

We make a number of simplifications and improvements to the group 
messaging service. They aim at readability/maintainability of the code
as well as scalability.

The series is based on commit f9c935db8086 ("tipc: fix problems with
multipoint-to-point flow control) which has been applied to 'net' but
not yet to 'net-next'.

Jon Maloy (9):
  tipc: a couple of cleanups
  tipc: let group member stay in JOINED mode if unable to reclaim
  tipc: adjustment to group member FSM
  tipc: create group member event messages when they are needed
  tipc: simplify group LEAVE sequence
  tipc: send out join messages as soon as new member is discovered
  tipc: add option to suppress PUBLISH events for pre-existing
    publications
  tipc: improve groupcast scope handling
  tipc: improve poll() for group member socket

 include/uapi/linux/tipc.h |   7 +-
 net/tipc/group.c          | 329 +++++++++++++++++++++++++---------------------
 net/tipc/group.h          |   8 +-
 net/tipc/name_table.c     |  55 ++++----
 net/tipc/name_table.h     |   6 +-
 net/tipc/server.c         |   6 +-
 net/tipc/server.h         |   7 +-
 net/tipc/socket.c         | 100 ++++++++------
 net/tipc/subscr.c         |  20 ++-
 net/tipc/subscr.h         |   2 +-
 10 files changed, 298 insertions(+), 242 deletions(-)

-- 
2.1.4

             reply	other threads:[~2018-01-08 19:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 19:34 Jon Maloy [this message]
2018-01-08 19:34 ` [net-next 1/9] tipc: a couple of cleanups Jon Maloy
2018-01-08 19:34 ` [net-next 2/9] tipc: let group member stay in JOINED mode if unable to reclaim Jon Maloy
2018-01-08 19:34 ` [net-next 3/9] tipc: adjustment to group member FSM Jon Maloy
2018-01-08 19:34 ` [net-next 4/9] tipc: create group member event messages when they are needed Jon Maloy
2018-01-08 19:34 ` [net-next 5/9] tipc: simplify group LEAVE sequence Jon Maloy
2018-01-08 19:34 ` [net-next 6/9] tipc: send out join messages as soon as new member is discovered Jon Maloy
2018-01-08 19:34 ` [net-next 7/9] tipc: add option to suppress PUBLISH events for pre-existing publications Jon Maloy
2018-01-08 19:34 ` [net-next 8/9] tipc: improve groupcast scope handling Jon Maloy
2018-01-08 19:34 ` [net-next 9/9] tipc: improve poll() for group member socket Jon Maloy
2018-01-09 17:36 ` [net-next 0/9] tipc: improvements to group messaging David Miller
  -- strict thread matches above, loose matches on Subject: below --
2018-01-08 20:03 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=1515440080-27377-1-git-send-email-jon.maloy@ericsson.com \
    --to=jon.maloy@ericsson.com \
    --cc=canh.d.luu@dektech.com.au \
    --cc=davem@davemloft.net \
    --cc=hoang.h.le@dektech.com.au \
    --cc=mohan.krishna.ghanta.krishnamurthy@ericsson.com \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=tung.q.nguyen@dektech.com.au \
    --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).