All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>,
	Seth Jennings <sjenning@linux.vnet.ibm.com>
Cc: Nitin Gupta <ngupta@vflare.org>, Greg KH <greg@kroah.com>,
	gregkh@suse.de, devel@driverdev.osuosl.org,
	cascardo@holoscopio.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, brking@linux.vnet.ibm.com,
	rcj@linux.vnet.ibm.com
Subject: RE: [PATCH v2 0/3] staging: zcache: xcfmalloc support
Date: Thu, 15 Sep 2011 15:27:07 -0700 (PDT)	[thread overview]
Message-ID: <504b4342-e6b0-4544-b81c-ca41240ac5bf@default> (raw)
In-Reply-To: <1316125062.16137.80.camel@nimitz>

> From: Dave Hansen [mailto:dave@linux.vnet.ibm.com]
> Subject: Re: [PATCH v2 0/3] staging: zcache: xcfmalloc support
> 
> On Thu, 2011-09-15 at 14:24 -0500, Seth Jennings wrote:
> > How would you suggest that I measure xcfmalloc performance on a "very
> > large set of workloads".  I guess another form of that question is: How
> > did xvmalloc do this?
> 
> Well, it didn't have a competitor, so this probably wasn't done. :)
> 
> I'd like to see a microbenchmarky sort of thing.  Do a million (or 100
> million, whatever) allocations, and time it for both allocators doing
> the same thing.  You just need to do the *same* allocations for both.

One suggestion:  We already know xvmalloc sucks IF the workload has
poor compression for most pages.  We are looking to understand if xcfmalloc
is [very**N] bad when xvmalloc is good.  So please measure BIG-NUMBER
allocations where compression is known to be OK on average (which is,
I think, a large fraction of workloads), rather than workloads where
xvmalloc already sucks.

WARNING: multiple messages have this Message-ID (diff)
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>,
	Seth Jennings <sjenning@linux.vnet.ibm.com>
Cc: Nitin Gupta <ngupta@vflare.org>, Greg KH <greg@kroah.com>,
	gregkh@suse.de, devel@driverdev.osuosl.org,
	cascardo@holoscopio.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, brking@linux.vnet.ibm.com,
	rcj@linux.vnet.ibm.com
Subject: RE: [PATCH v2 0/3] staging: zcache: xcfmalloc support
Date: Thu, 15 Sep 2011 15:27:07 -0700 (PDT)	[thread overview]
Message-ID: <504b4342-e6b0-4544-b81c-ca41240ac5bf@default> (raw)
In-Reply-To: <1316125062.16137.80.camel@nimitz>

> From: Dave Hansen [mailto:dave@linux.vnet.ibm.com]
> Subject: Re: [PATCH v2 0/3] staging: zcache: xcfmalloc support
> 
> On Thu, 2011-09-15 at 14:24 -0500, Seth Jennings wrote:
> > How would you suggest that I measure xcfmalloc performance on a "very
> > large set of workloads".  I guess another form of that question is: How
> > did xvmalloc do this?
> 
> Well, it didn't have a competitor, so this probably wasn't done. :)
> 
> I'd like to see a microbenchmarky sort of thing.  Do a million (or 100
> million, whatever) allocations, and time it for both allocators doing
> the same thing.  You just need to do the *same* allocations for both.

One suggestion:  We already know xvmalloc sucks IF the workload has
poor compression for most pages.  We are looking to understand if xcfmalloc
is [very**N] bad when xvmalloc is good.  So please measure BIG-NUMBER
allocations where compression is known to be OK on average (which is,
I think, a large fraction of workloads), rather than workloads where
xvmalloc already sucks.

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-09-15 22:27 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07 14:09 [PATCH v2 0/3] staging: zcache: xcfmalloc support Seth Jennings
2011-09-07 14:09 ` Seth Jennings
2011-09-07 14:09 ` [PATCH v2 1/3] staging: zcache: xcfmalloc memory allocator for zcache Seth Jennings
2011-09-07 14:09   ` Seth Jennings
2011-09-07 14:09 ` [PATCH v2 2/3] staging: zcache: replace xvmalloc with xcfmalloc Seth Jennings
2011-09-07 14:09   ` Seth Jennings
2011-09-07 14:09 ` [PATCH v2 3/3] staging: zcache: add zv_page_count and zv_desc_count Seth Jennings
2011-09-07 14:09   ` Seth Jennings
2011-09-09 20:34 ` [PATCH v2 0/3] staging: zcache: xcfmalloc support Greg KH
2011-09-09 20:34   ` Greg KH
2011-09-10  2:41   ` Nitin Gupta
2011-09-10  2:41     ` Nitin Gupta
2011-09-12 14:35     ` Seth Jennings
2011-09-12 14:35       ` Seth Jennings
2011-09-13  1:55       ` Nitin Gupta
2011-09-13  1:55         ` Nitin Gupta
2011-09-13 15:58         ` Seth Jennings
2011-09-13 15:58           ` Seth Jennings
2011-09-13 21:18           ` Nitin Gupta
2011-09-13 21:18             ` Nitin Gupta
2011-09-15 16:31             ` Seth Jennings
2011-09-15 16:31               ` Seth Jennings
2011-09-15 17:29               ` Dan Magenheimer
2011-09-15 17:29                 ` Dan Magenheimer
2011-09-15 19:24                 ` Seth Jennings
2011-09-15 19:24                   ` Seth Jennings
2011-09-15 20:07                   ` Dan Magenheimer
2011-09-15 20:07                     ` Dan Magenheimer
2011-10-03 15:59                     ` Dave Hansen
2011-10-03 15:59                       ` Dave Hansen
2011-10-03 17:54                       ` Nitin Gupta
2011-10-03 17:54                         ` Nitin Gupta
2011-10-03 18:22                         ` Dave Hansen
2011-10-03 18:22                           ` Dave Hansen
2011-10-05  1:03                           ` Dan Magenheimer
2011-10-05  1:03                             ` Dan Magenheimer
2011-09-15 22:17                   ` Dave Hansen
2011-09-15 22:17                     ` Dave Hansen
2011-09-15 22:27                     ` Dan Magenheimer [this message]
2011-09-15 22:27                       ` Dan Magenheimer
2011-09-16 17:36                     ` Nitin Gupta
2011-09-16 17:36                       ` Nitin Gupta
2011-09-16 17:52                   ` Nitin Gupta
2011-09-16 17:52                     ` Nitin Gupta
2011-09-16 17:46               ` Nitin Gupta
2011-09-16 17:46                 ` Nitin Gupta
2011-09-16 18:33                 ` Seth Jennings
2011-09-16 18:33                   ` Seth Jennings
2011-11-01 17:30                 ` Dave Hansen
2011-11-01 17:30                   ` Dave Hansen
2011-11-01 18:35                   ` Dan Magenheimer
2011-11-01 18:35                     ` Dan Magenheimer
2011-11-02  2:42                     ` Nitin Gupta
2011-11-02  2:42                       ` Nitin Gupta
2011-09-29 17:47 ` Seth Jennings
2011-09-29 17:47   ` 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=504b4342-e6b0-4544-b81c-ca41240ac5bf@default \
    --to=dan.magenheimer@oracle.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=cascardo@holoscopio.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ngupta@vflare.org \
    --cc=rcj@linux.vnet.ibm.com \
    --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 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.