From: Darren Hart <dvhltc@us.ibm.com>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Ravikiran G Thirumalai <kiran@scalex86.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
shai@scalex86.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [rfc] [patch 1/2 ] Process private hash tables for private futexes
Date: Thu, 23 Apr 2009 10:30:23 -0700 [thread overview]
Message-ID: <49F0A5AF.5080906@us.ibm.com> (raw)
In-Reply-To: <49C88616.9030307@cosmosbay.com>
Eric Dumazet wrote:
>
> + futex_queues = alloc_large_system_hash("futexes",
> + sizeof(struct futex_hash_bucket),
> + nr_slots,
> + 0, /* scale : unused */
> + 0, /* flags */
> + NULL, /* shift */
> + &futex_hash_mask,
> + nr_slots);
OK, so I'm a little late to the party, apologies.
Minor nit (from someone who has been spending a lot of time in futex.c
trying to clean things up recently :-). Let's not comment each argument
individually. It needlessly lengthens the code. The interested user
can easily look up alloc_large_system_hash. If you feel a comment is
really needed, consider a single line before the call... I gave this
some thought and couldn't think of anything you could put there that
wouldn't still send the interested reader over to page_alloc.c.
/* Allocate futex hashtable with... <whatever is special about this> */
futex_queues = alloc_large_system_hash("futexes",
sizeof(struct futex_hash_bucket),
nr_slots, 0, 0, NULL, &futex_hash_mask,
nr_slots);
--
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
next prev parent reply other threads:[~2009-04-23 17:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 4:46 [rfc] [patch 1/2 ] Process private hash tables for private futexes Ravikiran G Thirumalai
2009-03-21 4:52 ` [rfc] [patch 2/2 ] Sysctl to turn on/off private futex " Ravikiran G Thirumalai
2009-03-21 9:07 ` [rfc] [patch 1/2 ] Process private " Eric Dumazet
2009-03-21 11:55 ` [PATCH] futex: Dynamically size futexes hash table Eric Dumazet
2009-03-21 16:28 ` Ingo Molnar
2009-03-22 4:54 ` [rfc] [patch 1/2 ] Process private hash tables for private futexes Ravikiran G Thirumalai
2009-03-22 8:17 ` Eric Dumazet
2009-03-23 20:28 ` Ravikiran G Thirumalai
2009-03-23 21:57 ` Eric Dumazet
2009-03-24 3:19 ` Ravikiran G Thirumalai
2009-03-24 3:33 ` Ravikiran G Thirumalai
2009-03-24 5:31 ` Eric Dumazet
2009-03-24 7:04 ` Eric Dumazet
2009-04-23 17:30 ` Darren Hart [this message]
2009-03-21 11:35 ` Andrew Morton
2009-03-22 4:15 ` Ravikiran G Thirumalai
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=49F0A5AF.5080906@us.ibm.com \
--to=dvhltc@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shai@scalex86.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