From: Tom Herbert <tom@herbertland.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: Tom Herbert <tom@quantonium.net>
Subject: [PATCH net-next 0/4] ila: Cleanup
Date: Wed, 27 Jun 2018 14:38:58 -0700 [thread overview]
Message-ID: <1530135542-10372-1-git-send-email-tom@quantonium.net> (raw)
Perform some cleanup in ILA code. This includes:
- Fix rhashtable walk for cases where nl dumps are done with muliple
function calls. Add a skip index to skip over entries in
a node that have been previously visitied. Call rhashtable_walk_peek
to avoid dropping items between calls to ila_nl_dump.
- Call alloc_bucket_spinlocks to create bucket locks.
- Split out module initialization and netlink definitions into
separate files.
- Add ILA_CMD_FLUSH netlink command to clear the ILA translation table.
Tom Herbert (4):
ila: Fix use of rhashtable walk in ila_xlat.c
ila: Call library function alloc_bucket_locks
ila: Create main ila source file
ila: Flush netlink command to clear xlat table
include/uapi/linux/ila.h | 1 +
net/ipv6/ila/Makefile | 2 +-
net/ipv6/ila/ila.h | 27 ++++-
net/ipv6/ila/ila_common.c | 30 -----
net/ipv6/ila/ila_main.c | 121 +++++++++++++++++++
net/ipv6/ila/ila_xlat.c | 291 +++++++++++++++++++++++-----------------------
6 files changed, 292 insertions(+), 180 deletions(-)
create mode 100644 net/ipv6/ila/ila_main.c
--
2.7.4
next reply other threads:[~2018-06-27 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 21:38 Tom Herbert [this message]
2018-06-27 21:38 ` [PATCH net-next 1/4] ila: Fix use of rhashtable walk in ila_xlat.c Tom Herbert
2018-06-27 21:39 ` [PATCH net-next 2/4] ila: Call library function alloc_bucket_locks Tom Herbert
2018-06-27 21:39 ` [PATCH net-next 3/4] ila: Create main ila source file Tom Herbert
2018-06-27 21:39 ` [PATCH net-next 4/4] ila: Flush netlink command to clear xlat table Tom Herbert
2018-06-29 2:33 ` [PATCH net-next 0/4] ila: Cleanup 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=1530135542-10372-1-git-send-email-tom@quantonium.net \
--to=tom@herbertland.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tom@quantonium.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