From: Avi Kivity <avi@redhat.com>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: Huang Shijie <shijie8@gmail.com>,
akpm@linux-foundation.org, hugh.dickins@tiscali.co.uk,
linux-mm@kvack.org
Subject: Re: [PATCH] kvm : remove redundant initialization of page->private
Date: Wed, 10 Mar 2010 12:19:48 +0200 [thread overview]
Message-ID: <4B977244.4010603@redhat.com> (raw)
In-Reply-To: <1268065219.1254.12.camel@barrios-desktop>
On 03/08/2010 06:20 PM, Minchan Kim wrote:
> On Mon, 2010-03-08 at 17:33 +0800, Huang Shijie wrote:
>
>> The prep_new_page() will call set_page_private(page, 0) to initiate
>> the page.
>>
>> So the code is redundant.
>>
>> Signed-off-by: Huang Shijie<shijie8@gmail.com>
>> ---
>> mm/shmem.c | 2 --
>> 1 files changed, 0 insertions(+), 2 deletions(-)
>>
>> diff --git a/mm/shmem.c b/mm/shmem.c
>> index eef4ebe..dde4363 100644
>> --- a/mm/shmem.c
>> +++ b/mm/shmem.c
>> @@ -433,8 +433,6 @@ static swp_entry_t *shmem_swp_alloc(struct shmem_inode_info *info, unsigned long
>>
>> spin_unlock(&info->lock);
>> page = shmem_dir_alloc(mapping_gfp_mask(inode->i_mapping));
>> - if (page)
>> - set_page_private(page, 0);
>> spin_lock(&info->lock);
>>
>> if (!page) {
>>
> And I found another place while I review the code.
>
> > From e64322cde914e43d080d8f3be6f72459d809a934 Mon Sep 17 00:00:00 2001
> From: Minchan Kim<barrios@barrios-desktop.(none)>
> Date: Tue, 9 Mar 2010 01:09:56 +0900
> Subject: [PATCH] kvm : remove redundant initialization of page->private.
>
> The prep_new_page() in page allocator calls set_page_private(page, 0).
> So we don't need to reinitialize private of page.
>
> Signed-off-by: Minchan Kim<minchan.kim@gmail.com>
> Cc: Avi Kivity<avi@redhat.com>
> ---
> arch/x86/kvm/mmu.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index 741373e..9851d0e 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -326,7 +326,6 @@ static int mmu_topup_memory_cache_page(struct
> kvm_mmu_memory_cache *cache,
> page = alloc_page(GFP_KERNEL);
> if (!page)
> return -ENOMEM;
> - set_page_private(page, 0);
> cache->objects[cache->nobjs++] = page_address(page);
> }
> return 0;
>
Whitespace damage, please resend.
--
error compiling committee.c: too many arguments to function
--
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>
next prev parent reply other threads:[~2010-03-10 10:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 9:33 [PATCH] shmem : remove redundant code Huang Shijie
2010-03-08 16:04 ` Minchan Kim
2010-03-09 2:02 ` Huang Shijie
2010-03-08 16:20 ` [PATCH] kvm : remove redundant initialization of page->private Minchan Kim
2010-03-10 10:19 ` Avi Kivity [this message]
2010-03-10 14:31 ` Minchan Kim
2010-03-11 7:42 ` Avi Kivity
2010-03-11 8:51 ` Jan Kiszka
2010-03-11 8:55 ` Avi Kivity
2010-03-11 18:43 ` Hugh Dickins
2010-03-09 21:25 ` [PATCH] shmem : remove redundant code Hugh Dickins
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=4B977244.4010603@redhat.com \
--to=avi@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=shijie8@gmail.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.