From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: tgraf@suug.ch, netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] rhashtable: Get rid of raw table walkers part 1
Date: Fri, 19 Aug 2016 14:40:51 -0700 (PDT) [thread overview]
Message-ID: <20160819.144051.306029724958680678.davem@davemloft.net> (raw)
In-Reply-To: <20160818084854.GA11502@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Thu, 18 Aug 2016 16:48:54 +0800
> This series starts the process of getting rid of all raw rhashtable
> walkers (e.g., using any of the rht_for_each helpers) from the
> kernel.
>
> We need to do this before I can fix the resize kmalloc failure issue
> by using multi-layered tables.
>
> We should do this anyway because almost all raw table walkers are
> already buggy in that they don't handle multiple rhashtables during
> a resize.
Series applied to net-next with v2 of patch #3.
> Dave/Tomas, please keep an eye out for any new patches that try
> to introduce raw table walkers and nack them.
Ok.
prev parent reply other threads:[~2016-08-19 21:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 8:48 [PATCH 0/3] rhashtable: Get rid of raw table walkers part 1 Herbert Xu
2016-08-18 8:50 ` [PATCH 1/3] rhashtable: Remove GFP flag from rhashtable_walk_init Herbert Xu
2016-08-19 16:25 ` Thomas Graf
2016-08-19 16:38 ` Herbert Xu
2016-08-18 8:50 ` [PATCH 2/3] MAINTAINERS: Add extra rhashtable maintainer Herbert Xu
2016-08-19 16:25 ` Thomas Graf
2016-08-18 8:50 ` [PATCH 3/3] netlink: Use rhashtable walk interface in diag dump Herbert Xu
2016-08-19 8:09 ` Herbert Xu
2016-08-19 8:21 ` [v2 PATCH " Herbert Xu
2016-08-19 16:32 ` Thomas Graf
2016-08-19 16:39 ` Herbert Xu
2016-08-19 16:34 ` [PATCH 0/3] rhashtable: Get rid of raw table walkers part 1 Thomas Graf
2016-08-19 21:40 ` David Miller [this message]
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=20160819.144051.306029724958680678.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).