From: Michal Hocko <mhocko@kernel.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Florian Westphal <fw@strlen.de>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Michal Hocko <mhocko@suse.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Thomas Graf <tgraf@suug.ch>
Subject: [PATCH 0/3] replace few other kvmalloc open coded variants
Date: Wed, 31 May 2017 17:51:42 +0200 [thread overview]
Message-ID: <20170531155145.17111-1-mhocko@kernel.org> (raw)
Hi,
while doing something unrelated I've noticed these few open coded
kvmalloc variants so let's replace them with the library function. Each
patch can be merged separately so I hope I've CCed proper people. This
is based on the current linux-next.
Shortlog
Michal Hocko (3):
fs/file: replace alloc_fdmem with kvmalloc alternative
lib/rhashtable.c: use kvzalloc in bucket_table_alloc when possible
netfilter: use kvmalloc xt_alloc_table_info
Diffstat
fs/file.c | 22 ++++------------------
lib/rhashtable.c | 7 +++----
net/netfilter/x_tables.c | 12 ++++--------
3 files changed, 11 insertions(+), 30 deletions(-)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-05-31 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 15:51 Michal Hocko [this message]
2017-05-31 15:51 ` [PATCH 1/3] fs/file: replace alloc_fdmem with kvmalloc alternative Michal Hocko
2017-05-31 15:51 ` [PATCH 2/3] lib/rhashtable.c: use kvzalloc in bucket_table_alloc when possible Michal Hocko
2017-05-31 15:51 ` [PATCH 3/3] netfilter: use kvmalloc xt_alloc_table_info Michal Hocko
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=20170531155145.17111-1-mhocko@kernel.org \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=fw@strlen.de \
--cc=herbert@gondor.apana.org.au \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pablo@netfilter.org \
--cc=tgraf@suug.ch \
--cc=viro@zeniv.linux.org.uk \
/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).