From: Andrea Righi <righi.andrea@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] mm: unify pmd_free() implementation
Date: Mon, 28 Jul 2008 18:17:29 +0200 [thread overview]
Message-ID: <488DF119.2000004@gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0807280851130.3486@nehalem.linux-foundation.org>
Linus Torvalds wrote:
>
> On Mon, 28 Jul 2008, Andrea Righi wrote:
>> Move multiple definitions of pmd_free() from different include/asm-* into
>> mm/util.c.
>
> But this is horrible, because it forces a totally unnecessary function
> call for that empty function.
>
> Yeah, the function will be cheap, but the call itself will not be (it's a
> C language barrier and basically disables optimizations around it, causing
> thigns like register spill/reload for no good reason).
>
> Linus
yep! clear.
Ok, in this case wouldn't be better at least to define pud_free() as:
static inline pud_free(struct mm_struct *mm, pmd_t *pmd)
{
}
in include/asm-generic/pgtable-nopmd.h, just to avoid the warning
on x86 without PAE?
Thanks for the explanation,
-Andrea
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Righi <righi.andrea@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] mm: unify pmd_free() implementation
Date: Mon, 28 Jul 2008 18:17:29 +0200 [thread overview]
Message-ID: <488DF119.2000004@gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0807280851130.3486@nehalem.linux-foundation.org>
Linus Torvalds wrote:
>
> On Mon, 28 Jul 2008, Andrea Righi wrote:
>> Move multiple definitions of pmd_free() from different include/asm-* into
>> mm/util.c.
>
> But this is horrible, because it forces a totally unnecessary function
> call for that empty function.
>
> Yeah, the function will be cheap, but the call itself will not be (it's a
> C language barrier and basically disables optimizations around it, causing
> thigns like register spill/reload for no good reason).
>
> Linus
yep! clear.
Ok, in this case wouldn't be better at least to define pud_free() as:
static inline pud_free(struct mm_struct *mm, pmd_t *pmd)
{
}
in include/asm-generic/pgtable-nopmd.h, just to avoid the warning
on x86 without PAE?
Thanks for the explanation,
-Andrea
--
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:[~2008-07-28 16:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 15:51 [PATCH 1/1] mm: unify pmd_free() implementation Andrea Righi
2008-07-28 15:51 ` Andrea Righi
2008-07-28 15:53 ` Linus Torvalds
2008-07-28 15:53 ` Linus Torvalds
2008-07-28 16:17 ` Andrea Righi [this message]
2008-07-28 16:17 ` Andrea Righi
2008-07-28 16:27 ` KOSAKI Motohiro
2008-07-28 16:27 ` KOSAKI Motohiro
2008-07-28 17:19 ` Andrea Righi
2008-07-28 17:19 ` Andrea Righi
2008-07-28 20:30 ` Andrew Morton
2008-07-28 20:30 ` Andrew Morton
2008-07-28 20:46 ` Jeremy Fitzhardinge
2008-07-28 20:46 ` Jeremy Fitzhardinge
2008-07-28 22:53 ` [PATCH 1/1] mm: unify pmd_free() and __pmd_free_tlb() implementation Andrea Righi
2008-07-28 22:53 ` Andrea Righi
2008-07-31 16:17 ` Ingo Molnar
2008-07-31 16:17 ` Ingo Molnar
2008-07-31 16:59 ` Andrea Righi
2008-07-31 16:59 ` Andrea Righi
2008-07-28 16:17 ` [PATCH 1/1] mm: unify pmd_free() implementation James Bottomley
2008-07-28 16:17 ` James Bottomley
2008-07-28 16:45 ` Linus Torvalds
2008-07-28 16:45 ` Linus Torvalds
2008-07-28 16:58 ` James Bottomley
2008-07-28 16:58 ` James Bottomley
2008-07-28 17:10 ` Linus Torvalds
2008-07-28 17:10 ` Linus Torvalds
2008-07-28 20:08 ` [PATCH 1/1] mm: unify pmd_free() implementation -> instrumentation Mathieu Desnoyers
2008-07-28 20:08 ` Mathieu Desnoyers
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=488DF119.2000004@gmail.com \
--to=righi.andrea@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.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 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.