From: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Nitin Gupta <ngupta@vflare.org>,
Robert Jennings <rcj@linux.vnet.ibm.com>,
linux-mm@kvack.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] zsmalloc: add page table mapping method
Date: Sun, 22 Jul 2012 19:33:40 -0500 [thread overview]
Message-ID: <500C9BE4.70108@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120723002655.GC4037@bbox>
On 07/22/2012 07:26 PM, Minchan Kim wrote:
> On Wed, Jul 18, 2012 at 11:55:56AM -0500, Seth Jennings wrote:
>> This patchset provides page mapping via the page table.
>> On some archs, most notably ARM, this method has been
>> demonstrated to be faster than copying.
>>
>> The logic controlling the method selection (copy vs page table)
>> is controlled by the definition of USE_PGTABLE_MAPPING which
>> is/can be defined for any arch that performs better with page
>> table mapping.
>>
>> Signed-off-by: Seth Jennings <sjenning@linux.vnet.ibm.com>
>> ---
>> drivers/staging/zsmalloc/zsmalloc-main.c | 182 ++++++++++++++++++++++--------
>> drivers/staging/zsmalloc/zsmalloc_int.h | 6 -
>> 2 files changed, 134 insertions(+), 54 deletions(-)
>>
>> diff --git a/drivers/staging/zsmalloc/zsmalloc-main.c b/drivers/staging/zsmalloc/zsmalloc-main.c
>> index b86133f..defe350 100644
>> --- a/drivers/staging/zsmalloc/zsmalloc-main.c
>> +++ b/drivers/staging/zsmalloc/zsmalloc-main.c
>> @@ -89,6 +89,30 @@
>> #define CLASS_IDX_MASK ((1 << CLASS_IDX_BITS) - 1)
>> #define FULLNESS_MASK ((1 << FULLNESS_BITS) - 1)
>>
>> +/*
>> + * By default, zsmalloc uses a copy-based object mapping method to access
>> + * allocations that span two pages. However, if a particular architecture
>> + * 1) Implements local_flush_tlb_kernel_range() and 2) Performs VM mapping
>> + * faster than copying, then it should be added here so that
>
> How about adding your benchmark url?
>
>> + * USE_PGTABLE_MAPPING is defined. This causes zsmalloc to use page table
>> + * mapping rather than copying
>> + * for object mapping.
>
> unnecessary new line.
Since these aren't functional issues with the code, if I
_promise_ to send a follow-up patch to address these, can I
get your Ack?
--
Seth
--
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: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Nitin Gupta <ngupta@vflare.org>,
Robert Jennings <rcj@linux.vnet.ibm.com>,
linux-mm@kvack.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] zsmalloc: add page table mapping method
Date: Sun, 22 Jul 2012 19:33:40 -0500 [thread overview]
Message-ID: <500C9BE4.70108@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120723002655.GC4037@bbox>
On 07/22/2012 07:26 PM, Minchan Kim wrote:
> On Wed, Jul 18, 2012 at 11:55:56AM -0500, Seth Jennings wrote:
>> This patchset provides page mapping via the page table.
>> On some archs, most notably ARM, this method has been
>> demonstrated to be faster than copying.
>>
>> The logic controlling the method selection (copy vs page table)
>> is controlled by the definition of USE_PGTABLE_MAPPING which
>> is/can be defined for any arch that performs better with page
>> table mapping.
>>
>> Signed-off-by: Seth Jennings <sjenning@linux.vnet.ibm.com>
>> ---
>> drivers/staging/zsmalloc/zsmalloc-main.c | 182 ++++++++++++++++++++++--------
>> drivers/staging/zsmalloc/zsmalloc_int.h | 6 -
>> 2 files changed, 134 insertions(+), 54 deletions(-)
>>
>> diff --git a/drivers/staging/zsmalloc/zsmalloc-main.c b/drivers/staging/zsmalloc/zsmalloc-main.c
>> index b86133f..defe350 100644
>> --- a/drivers/staging/zsmalloc/zsmalloc-main.c
>> +++ b/drivers/staging/zsmalloc/zsmalloc-main.c
>> @@ -89,6 +89,30 @@
>> #define CLASS_IDX_MASK ((1 << CLASS_IDX_BITS) - 1)
>> #define FULLNESS_MASK ((1 << FULLNESS_BITS) - 1)
>>
>> +/*
>> + * By default, zsmalloc uses a copy-based object mapping method to access
>> + * allocations that span two pages. However, if a particular architecture
>> + * 1) Implements local_flush_tlb_kernel_range() and 2) Performs VM mapping
>> + * faster than copying, then it should be added here so that
>
> How about adding your benchmark url?
>
>> + * USE_PGTABLE_MAPPING is defined. This causes zsmalloc to use page table
>> + * mapping rather than copying
>> + * for object mapping.
>
> unnecessary new line.
Since these aren't functional issues with the code, if I
_promise_ to send a follow-up patch to address these, can I
get your Ack?
--
Seth
next prev parent reply other threads:[~2012-07-23 0:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 16:55 [PATCH 1/3] zsmalloc: s/firstpage/page in new copy map funcs Seth Jennings
2012-07-18 16:55 ` Seth Jennings
2012-07-18 16:55 ` [PATCH 2/3] zsmalloc: prevent mappping in interrupt context Seth Jennings
2012-07-18 16:55 ` Seth Jennings
2012-07-23 0:13 ` Minchan Kim
2012-07-23 0:13 ` Minchan Kim
2012-07-18 16:55 ` [PATCH 3/3] zsmalloc: add page table mapping method Seth Jennings
2012-07-18 16:55 ` Seth Jennings
2012-07-23 0:26 ` Minchan Kim
2012-07-23 0:26 ` Minchan Kim
2012-07-23 0:33 ` Seth Jennings [this message]
2012-07-23 0:33 ` Seth Jennings
2012-07-23 0:46 ` Minchan Kim
2012-07-23 0:46 ` Minchan Kim
2012-07-23 2:15 ` Nitin Gupta
2012-07-23 2:15 ` Nitin Gupta
2012-07-23 0:11 ` [PATCH 1/3] zsmalloc: s/firstpage/page in new copy map funcs Minchan Kim
2012-07-23 0:11 ` Minchan Kim
2012-07-23 22:10 ` Seth Jennings
2012-07-23 22:10 ` Seth Jennings
2012-07-23 22:27 ` Greg Kroah-Hartman
2012-07-23 22:27 ` Greg Kroah-Hartman
2012-07-24 2:24 ` Minchan Kim
2012-07-24 2:24 ` Minchan Kim
2012-07-24 14:54 ` Greg Kroah-Hartman
2012-07-24 14:54 ` Greg Kroah-Hartman
2012-08-08 4:57 ` Minchan Kim
2012-08-08 4:57 ` Minchan Kim
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=500C9BE4.70108@linux.vnet.ibm.com \
--to=sjenning@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dan.magenheimer@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=rcj@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.