From: "Luck, Tony" <tony.luck@intel.com>
To: Christoph Lameter <clameter@sgi.com>, akpm@osdl.org
Cc: Hugh Dickins <hugh@veritas.com>,
linux-ia64@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Lee Schermerhorn <lee.schermerhorn@hp.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
linux-mm@kvack.org, Andi Kleen <ak@suse.de>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: RE: [5/5] move_pages: 32bit support (i386,x86_64 and ia64)
Date: Wed, 24 May 2006 11:45:58 -0700 [thread overview]
Message-ID: <B8E391BBE9FE384DAA4C5C003888BE6F0693FC5B@scsmsx401.amr.corp.intel.com> (raw)
> 2. There is a whole range of syscalls missing for ia64 that I basically
> interpolated from elsewhere.
I've been thinking of dropping CONFIG_IA32_SUPPORT completely from ia64.
I've heard no complaints that new syscalls are not being added to the
ia32 compat side ... which is an indication that people are not
actively using this. Some OSDs have been building with this
turned off for a while now (perhaps in preparation for "Montecito"
which no longer has h/w support for the x86 instruction set, or
perhaps because it represnts a huge block of lightly/barely tested
code that will have its share of support issues).
I suppose I should do this by adding an entry to
Documentation/feature-removal-schedule.txt
Any thoughts on the timeline for this? Is Dec 31, 2006 too soon?
(or not soon enough!?).
-Tony
--
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 reply other threads:[~2006-05-24 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 18:45 Luck, Tony [this message]
2006-05-24 18:58 ` Andrew Morton
2006-05-24 19:01 ` Christoph Lameter
2006-05-24 20:38 ` dropping CONFIG_IA32_SUPPORT from ia64 Bjorn Helgaas
2006-05-25 1:32 ` Matt Taggart
2006-05-25 3:30 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-05-24 19:18 [5/5] move_pages: 32bit support (i386,x86_64 and ia64) Luck, Tony
2006-05-23 17:43 [0/5] sys_move_pages() updates Christoph Lameter
2006-05-23 17:44 ` [5/5] move_pages: 32bit support (i386,x86_64 and ia64) Christoph Lameter
2006-05-24 20:32 ` Andrew Morton
2006-05-24 20:33 ` Jens Axboe
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=B8E391BBE9FE384DAA4C5C003888BE6F0693FC5B@scsmsx401.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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