From: Dave Hansen <haveblue@us.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: [RFC][PATCH 0/9] generic PAGE_SIZE infrastructure (v4)
Date: Thu, 31 Aug 2006 14:03:12 -0700 [thread overview]
Message-ID: <1157058192.28577.33.camel@localhost.localdomain> (raw)
In-Reply-To: <17654.11889.933070.539839@cargo.ozlabs.ibm.com>
On Thu, 2006-08-31 at 10:33 +1000, Paul Mackerras wrote:
> Dave Hansen writes:
> > Why am I doing this? The OpenVZ beancounter patch hooks into the
> > alloc_thread_info() path, but only in two architectures. It is silly
> > to patch each and every architecture when they all just do the same
> > thing. This is the first step to have a single place in which to
> > do alloc_thread_info(). Oh, and this series removes about 300 lines
> > of code.
>
> ... at the price of making the Kconfig help text more generic and
> therefore possibly confusing on some platforms.
>
> I really don't see much value in doing all this.
The value for me is that this makes it much easier to add generic kernel
features. There have been way too many times that I've made some
arch-independent change which required going and fixing up the *same*
code in every single architecture.
-- Dave
--
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>
prev parent reply other threads:[~2006-08-31 21:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 22:16 Dave Hansen
2006-08-30 22:16 ` [RFC][PATCH 2/9] conditionally define generic get_order() (ARCH_HAS_GET_ORDER) Dave Hansen
2006-08-31 18:41 ` Haavard Skinnemoen
2006-08-31 19:51 ` Dave Hansen
2006-08-30 22:16 ` [RFC][PATCH 1/9] put alignment macros in align.h Dave Hansen
2006-08-30 22:16 ` [RFC][PATCH 3/9] actual generic PAGE_SIZE infrastructure Dave Hansen
2006-08-31 0:08 ` Christoph Lameter
2006-08-31 17:57 ` Dave Hansen
2006-08-31 18:06 ` Christoph Lameter
2006-08-31 20:50 ` Dave Hansen
2006-09-05 11:20 ` Martin Waitz
2006-09-05 16:47 ` Dave Hansen
2006-10-17 7:29 ` Qi Yong
2006-08-30 22:16 ` [RFC][PATCH 4/9] ia64 generic PAGE_SIZE Dave Hansen
2006-08-30 23:57 ` Christoph Lameter
2006-08-31 17:38 ` Dave Hansen
2006-08-31 17:39 ` Christoph Lameter
2006-08-30 22:16 ` [RFC][PATCH 5/9] sparc64 " Dave Hansen
2006-08-30 22:27 ` David Miller, Dave Hansen
2006-08-30 22:16 ` [RFC][PATCH 6/9] mips " Dave Hansen
2006-08-30 22:16 ` [RFC][PATCH 7/9] parisc " Dave Hansen
2006-08-30 22:40 ` Kyle McMartin
2006-08-30 22:48 ` Dave Hansen
2006-08-30 22:16 ` [RFC][PATCH 8/9] powerpc " Dave Hansen
2006-08-30 22:16 ` [RFC][PATCH 9/9] convert the "easy" architectures to " Dave Hansen
2006-08-31 0:33 ` [RFC][PATCH 0/9] generic PAGE_SIZE infrastructure (v4) Paul Mackerras
2006-08-31 21:03 ` Dave Hansen [this message]
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=1157058192.28577.33.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox