From: Greg KH <greg@kroah.com>
To: Seth Jennings <sjenning@linux.vnet.ibm.com>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org,
dan.magenheimer@oracle.com, ngupta@vflare.org,
cascardo@holoscopio.com, rdunlap@xenotime.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] staging: zcache: xcfmalloc memory allocator for zcache
Date: Tue, 6 Sep 2011 16:51:29 -0700 [thread overview]
Message-ID: <20110906235129.GA26281@kroah.com> (raw)
In-Reply-To: <4E5FA81F.6060607@linux.vnet.ibm.com>
On Thu, Sep 01, 2011 at 10:43:27AM -0500, Seth Jennings wrote:
> On 08/31/2011 09:40 AM, Seth Jennings wrote:
>
> > +static struct xcf_blkdesc *xcf_find_remove_block(struct xcf_pool *pool,
> > + int size, int blocknum)
> > +{
> > + int flindex, i;
> > + struct xcf_blkdesc *desc = NULL;
> > +
> > + flindex = xcf_size_to_flindex(size + sizeof(struct xcf_blkhdr));
> > +
> > + /* look for best fit */
> > + if (pool->freelists[flindex])
> > + goto remove;
> > +
> > + /* if this is the last block allowed in the allocation, we shouldn't
> > + * consider smaller blocks. it's all or nothing now */
> > + if (blocknum == XCF_MAX_BLOCKS_PER_ALLOC) {
>
> In gathering my performance numbers for Dan, I discovered I introduced
> a regression by making a late change in my development.
>
> This line should be:
> if (blocknum != XCF_MAX_BLOCKS_PER_ALLOC) {
>
> This regression actually causes xcfmalloc to have the same fragmentation
> issue as xvmalloc.
Ok, care to resend a tested and correct patch series then?
greg k-h
next prev parent reply other threads:[~2011-09-06 23:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 14:40 [PATCH 0/3] staging: zcache: xcfmalloc support Seth Jennings
2011-08-31 14:40 ` [PATCH 1/3] staging: zcache: xcfmalloc memory allocator for zcache Seth Jennings
2011-09-01 15:43 ` Seth Jennings
2011-09-06 23:51 ` Greg KH [this message]
2011-08-31 14:40 ` [PATCH 2/3] staging: zcache: replace xvmalloc with xcfmalloc Seth Jennings
2011-08-31 14:40 ` [PATCH 3/3] staging: zcache: add zv_page_count and zv_desc_count Seth Jennings
2011-08-31 19:46 ` [PATCH 0/3] staging: zcache: xcfmalloc support Dan Magenheimer
2011-08-31 22:06 ` Seth Jennings
2011-09-01 15:17 ` Dan Magenheimer
2011-09-01 16:33 ` Seth Jennings
2011-09-01 16:54 ` Dave Hansen
2011-09-01 22:01 ` Seth Jennings
2011-09-01 23:44 ` Dave Hansen
2011-09-01 22:42 ` Seth Jennings
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=20110906235129.GA26281@kroah.com \
--to=greg@kroah.com \
--cc=cascardo@holoscopio.com \
--cc=dan.magenheimer@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=rdunlap@xenotime.net \
--cc=sjenning@linux.vnet.ibm.com \
/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