From: Jon Maloy <jon.maloy@ericsson.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: tipc-discussion@lists.sourceforge.net,
mohan.krishna.ghanta.krishnamurthy@ericsson.com
Subject: [net-next 0/4] tipc: slim down name table
Date: Wed, 28 Mar 2018 16:58:19 +0200 [thread overview]
Message-ID: <1522249103-32714-1-git-send-email-jon.maloy@ericsson.com> (raw)
We clean up and improve the name binding table:
- Replace the memory consuming 'sub_sequence/service range' array with
an RB tree.
- Introduce support for overlapping service sequences/ranges
Jon Maloy (4):
tipc: replace name table service range array with rb tree
tipc: refactor name table translate function
tipc: permit overlapping service ranges in name table
tipc: tipc: rename address types in user api
include/uapi/linux/tipc.h | 32 +-
net/tipc/core.h | 1 +
net/tipc/link.c | 2 +-
net/tipc/name_distr.c | 90 +---
net/tipc/name_distr.h | 1 -
net/tipc/name_table.c | 1075 ++++++++++++++++++++-------------------------
net/tipc/name_table.h | 10 +-
net/tipc/net.c | 2 +-
net/tipc/node.c | 4 +-
net/tipc/socket.c | 4 +-
net/tipc/subscr.h | 4 +-
11 files changed, 538 insertions(+), 687 deletions(-)
--
2.1.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:[~2018-03-28 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 14:58 Jon Maloy [this message]
2018-03-28 14:58 ` [net-next 1/4] tipc: replace name table service range array with rb tree Jon Maloy
2018-03-29 18:46 ` David Miller
2018-03-28 14:58 ` [net-next 2/4] tipc: refactor name table translate function Jon Maloy
2018-03-28 14:58 ` [net-next 3/4] tipc: permit overlapping service ranges in name table Jon Maloy
2018-03-28 14:58 ` [net-next 4/4] tipc: tipc: rename address types in user api 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=1522249103-32714-1-git-send-email-jon.maloy@ericsson.com \
--to=jon.maloy@ericsson.com \
--cc=davem@davemloft.net \
--cc=mohan.krishna.ghanta.krishnamurthy@ericsson.com \
--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).