From: Kent Overstreet <kent.overstreet@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
Dave Hansen <dave.hansen@intel.com>,
Matthew Wilcox <willy@infradead.org>
Subject: [PATCH 0/6] flex_arrays -> genradix; prep work for bcachefs
Date: Fri, 7 Sep 2018 12:56:29 -0400 [thread overview]
Message-ID: <20180907165635.8469-1-kent.overstreet@gmail.com> (raw)
Generic radix trees are a dead simple radix tree implementation that can store
types of different sizes, needed for bcachefs.
The patch series was sent out previously and was pretty uncontroversial - this
is a respin that converts most users to just use kvmalloc.
Kent Overstreet (6):
openvswitch: convert to kvmalloc
md: convert to kvmalloc
selinux: convert to kvmalloc
Generic radix trees
proc: commit to genradix
Drop flex_arrays
Documentation/core-api/flexible-arrays.rst | 130 -------
Documentation/flexible-arrays.txt | 123 -------
drivers/md/raid5-ppl.c | 7 +-
drivers/md/raid5.c | 82 ++---
drivers/md/raid5.h | 9 +-
fs/proc/base.c | 43 +--
include/linux/flex_array.h | 149 --------
include/linux/generic-radix-tree.h | 222 ++++++++++++
include/linux/poison.h | 3 -
lib/Makefile | 5 +-
lib/flex_array.c | 398 ---------------------
lib/generic-radix-tree.c | 180 ++++++++++
net/openvswitch/flow.h | 1 -
net/openvswitch/flow_netlink.h | 1 -
net/openvswitch/flow_table.c | 51 +--
net/openvswitch/flow_table.h | 3 +-
security/selinux/ss/avtab.c | 40 +--
security/selinux/ss/avtab.h | 4 +-
security/selinux/ss/conditional.c | 6 +-
security/selinux/ss/policydb.c | 122 ++-----
security/selinux/ss/policydb.h | 12 +-
security/selinux/ss/services.c | 22 +-
tools/include/linux/poison.h | 3 -
23 files changed, 540 insertions(+), 1076 deletions(-)
delete mode 100644 Documentation/core-api/flexible-arrays.rst
delete mode 100644 Documentation/flexible-arrays.txt
delete mode 100644 include/linux/flex_array.h
create mode 100644 include/linux/generic-radix-tree.h
delete mode 100644 lib/flex_array.c
create mode 100644 lib/generic-radix-tree.c
--
2.19.0.rc2
next reply other threads:[~2018-09-07 16:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 16:56 Kent Overstreet [this message]
2018-09-07 16:56 ` [PATCH 1/6] openvswitch: convert to kvmalloc Kent Overstreet
2018-09-07 17:19 ` Matthew Wilcox
2018-09-07 16:56 ` [PATCH 2/6] md: " Kent Overstreet
2018-09-07 17:49 ` Matthew Wilcox
2018-09-07 18:16 ` Kent Overstreet
2018-09-07 16:56 ` [PATCH 3/6] selinux: " Kent Overstreet
2018-09-07 17:08 ` Tetsuo Handa
2018-09-07 17:50 ` Kent Overstreet
2018-09-13 2:27 ` Paul Moore
2018-09-07 16:56 ` [PATCH 4/6] Generic radix trees Kent Overstreet
2018-09-10 23:18 ` [PATCH] Generic radix tree: add kernel-doc chapter Randy Dunlap
2018-09-07 16:56 ` [PATCH 5/6] proc: commit to genradix Kent Overstreet
2018-09-07 16:56 ` [PATCH 6/6] Drop flex_arrays Kent Overstreet
2018-09-07 18:49 ` Randy Dunlap
2018-12-13 12:30 ` Xin Long
2018-12-13 14:41 ` Matthew Wilcox
2018-12-13 15:51 ` Neil Horman
2018-12-13 16:45 ` Matthew Wilcox
2018-12-13 18:09 ` Neil Horman
2018-12-17 12:50 ` Kent Overstreet
2018-12-18 12:19 ` Neil Horman
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=20180907165635.8469-1-kent.overstreet@gmail.com \
--to=kent.overstreet@gmail.com \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.org \
/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).