From: Tim Chen <tim.c.chen@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH 1/2] tmpfs: Quick token library to allow scalable retrieval of tokens from token jar
Date: Wed, 26 May 2010 12:33:24 -0700 [thread overview]
Message-ID: <1274902404.31973.9394.camel@mudge.jf.intel.com> (raw)
In-Reply-To: <20100520160834.d537ccf6.akpm@linux-foundation.org>
Andrew,
I've fixed the issues that you brought up for this patch series. I have
sent out version 2 patches in separate mails.
I've followed up on one of your comments below to explain why I'm doing
things done differently from your suggestions.
On Thu, 2010-05-20 at 16:08 -0700, Andrew Morton wrote:
> > +
> > +struct qtoken {
> > + long pool; /* pool of free tokens */
> > + long total; /* total num of tokens */
> > +#ifdef CONFIG_SMP
> > + long init_cache_sz; /* initial cache size */
>
> I don't think that it si meaningful for any of these things to have
> negative values, so an unsigned type would be more appropriate.
>
> Did they really need to be `long'? Plain old `unsigned' might be more
> efficient, perhaps.
I've changed "pool" and "total" to unsigned long. However, since tmpfs
uses unsigned long for the free blocks, I have to use unsigned long
instead of unsigned for the token jar to maintain compatibility with
tmpfs.
Thank you for your review.
Regards,
Tim Chen
prev parent reply other threads:[~2010-05-26 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 23:34 tim
2010-05-20 23:08 ` Andrew Morton
2010-05-26 19:33 ` Tim Chen [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=1274902404.31973.9394.camel@mudge.jf.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome