All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <levinsasha928@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Josh Triplett <josh@joshtriplett.org>, Tejun Heo <tj@kernel.org>,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	paul.gortmaker@windriver.com
Subject: Re: [RFC 1/4] hashtable: introduce a small and naive hashtable
Date: Thu, 02 Aug 2012 18:34:46 +0200	[thread overview]
Message-ID: <501AAC26.6030703@gmail.com> (raw)
In-Reply-To: <87txwl1dsq.fsf@xmission.com>

On 08/02/2012 06:03 PM, Eric W. Biederman wrote:
> Sasha Levin <levinsasha928@gmail.com> writes:
>> On 08/02/2012 12:32 PM, Josh Triplett wrote:
>>> What about using a C99 flexible array member?  Kernel style prohibits
>>> variable-length arrays, but I don't think the same rationale applies to
>>> flexible array members.
>>>
>>> struct hash_table {
>>>     size_t count;
>>>     struct hlist_head buckets[];
>>> };
>>>
>>> #define DEFINE_HASH_TABLE(name, length) struct hash_table name = { .count = length, .buckets = { [0 ... (length - 1)] = HLIST_HEAD_INIT } }
>>
>> The limitation of this approach is that the struct hash_table variable
>> must be 'static', which is a bit limiting - see for example the use of
>> hashtable in 'struct user_namespace'.
> 
> You mean the hash table that was made static in 3.5?
> 
> You might want to try basing your patches on something a little more current.
> 
> Eric
> 

Heh, I've started working on it in April, and just returned to this. Didn't think about rebasing to something new.

will fix - Thanks!

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <levinsasha928@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Josh Triplett <josh@joshtriplett.org>, Tejun Heo <tj@kernel.org>,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	paul.gortmaker@windriver.com
Subject: Re: [RFC 1/4] hashtable: introduce a small and naive hashtable
Date: Thu, 02 Aug 2012 18:34:46 +0200	[thread overview]
Message-ID: <501AAC26.6030703@gmail.com> (raw)
In-Reply-To: <87txwl1dsq.fsf@xmission.com>

On 08/02/2012 06:03 PM, Eric W. Biederman wrote:
> Sasha Levin <levinsasha928@gmail.com> writes:
>> On 08/02/2012 12:32 PM, Josh Triplett wrote:
>>> What about using a C99 flexible array member?  Kernel style prohibits
>>> variable-length arrays, but I don't think the same rationale applies to
>>> flexible array members.
>>>
>>> struct hash_table {
>>>     size_t count;
>>>     struct hlist_head buckets[];
>>> };
>>>
>>> #define DEFINE_HASH_TABLE(name, length) struct hash_table name = { .count = length, .buckets = { [0 ... (length - 1)] = HLIST_HEAD_INIT } }
>>
>> The limitation of this approach is that the struct hash_table variable
>> must be 'static', which is a bit limiting - see for example the use of
>> hashtable in 'struct user_namespace'.
> 
> You mean the hash table that was made static in 3.5?
> 
> You might want to try basing your patches on something a little more current.
> 
> Eric
> 

Heh, I've started working on it in April, and just returned to this. Didn't think about rebasing to something new.

will fix - Thanks!

  reply	other threads:[~2012-08-02 16:34 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 18:05 [RFC 0/4] generic hashtable implementation Sasha Levin
2012-07-31 18:05 ` Sasha Levin
2012-07-31 18:05 ` [RFC 1/4] hashtable: introduce a small and naive hashtable Sasha Levin
2012-07-31 18:05   ` Sasha Levin
2012-07-31 18:23   ` Tejun Heo
2012-07-31 18:23     ` Tejun Heo
2012-07-31 20:31     ` Sasha Levin
2012-07-31 20:31       ` Sasha Levin
2012-08-01 18:19     ` Sasha Levin
2012-08-01 18:19       ` Sasha Levin
2012-08-01 18:21       ` Tejun Heo
2012-08-01 18:21         ` Tejun Heo
2012-08-01 18:24         ` Sasha Levin
2012-08-01 18:24           ` Sasha Levin
2012-08-01 18:27           ` Tejun Heo
2012-08-01 18:27             ` Tejun Heo
2012-08-01 19:06             ` Sasha Levin
2012-08-01 19:06               ` Sasha Levin
2012-08-01 20:24               ` Tejun Heo
2012-08-01 20:24                 ` Tejun Heo
2012-08-01 22:41                 ` Sasha Levin
2012-08-01 22:41                   ` Sasha Levin
2012-08-01 22:45                   ` Tejun Heo
2012-08-01 22:45                     ` Tejun Heo
2012-08-02 10:00                     ` Sasha Levin
2012-08-02 10:00                       ` Sasha Levin
2012-08-02 10:32                       ` Josh Triplett
2012-08-02 10:32                         ` Josh Triplett
2012-08-02 11:23                         ` Sasha Levin
2012-08-02 11:23                           ` Sasha Levin
2012-08-02 13:04                           ` Sasha Levin
2012-08-02 13:04                             ` Sasha Levin
2012-08-02 16:15                             ` Josh Triplett
2012-08-02 16:15                               ` Josh Triplett
2012-08-02 16:48                               ` Sasha Levin
2012-08-02 16:48                                 ` Sasha Levin
2012-08-02 17:44                                 ` Josh Triplett
2012-08-02 17:44                                   ` Josh Triplett
2012-08-02 17:54                                   ` Sasha Levin
2012-08-02 17:54                                     ` Sasha Levin
2012-08-02 20:41                                     ` Josh Triplett
2012-08-02 20:41                                       ` Josh Triplett
2012-08-02 21:47                                       ` Sasha Levin
2012-08-02 21:47                                         ` Sasha Levin
2012-08-03 17:59                                         ` Josh Triplett
2012-08-03 17:59                                           ` Josh Triplett
2012-08-02 16:03                           ` Eric W. Biederman
2012-08-02 16:03                             ` Eric W. Biederman
2012-08-02 16:34                             ` Sasha Levin [this message]
2012-08-02 16:34                               ` Sasha Levin
2012-08-02 16:40                               ` Eric W. Biederman
2012-08-02 16:40                                 ` Eric W. Biederman
2012-08-02 17:32                                 ` Linus Torvalds
2012-08-02 17:32                                   ` Linus Torvalds
2012-08-02 17:48                                   ` Eric Dumazet
2012-08-02 17:48                                     ` Eric Dumazet
2012-08-02 17:59                                   ` Josh Triplett
2012-08-02 17:59                                     ` Josh Triplett
2012-08-02 18:08                                     ` Linus Torvalds
2012-08-02 18:08                                       ` Linus Torvalds
2012-08-02 20:25                                       ` Josh Triplett
2012-08-02 20:25                                         ` Josh Triplett
2012-08-02 20:32                                         ` Linus Torvalds
2012-08-02 21:21                                           ` Josh Triplett
2012-08-02 21:21                                             ` Josh Triplett
2012-08-02 21:50                                             ` Linus Torvalds
2012-08-02 21:50                                               ` Linus Torvalds
2012-08-02  9:35             ` Josh Triplett
2012-08-02  9:35               ` Josh Triplett
2012-07-31 18:05 ` [RFC 2/4] user_ns: use new hashtable implementation Sasha Levin
2012-07-31 18:05   ` Sasha Levin
2012-07-31 18:05 ` [RFC 3/4] mm,ksm: " Sasha Levin
2012-07-31 18:05   ` Sasha Levin
2012-07-31 18:05 ` [RFC 4/4] workqueue: " Sasha Levin
2012-07-31 18:05   ` Sasha Levin

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=501AAC26.6030703@gmail.com \
    --to=levinsasha928@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.