linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: bert hubert <ahu@ds9a.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2-mm3
Date: Sat, 2 Aug 2003 16:42:05 -0700	[thread overview]
Message-ID: <20030802164205.5cc42edc.akpm@osdl.org> (raw)
In-Reply-To: <20030802223140.GA25501@outpost.ds9a.nl>

bert hubert <ahu@ds9a.nl> wrote:
>
> On Sat, Aug 02, 2003 at 03:22:02PM -0700, Andrew Morton wrote:
> 
> > . I don't think anyone has reported on whether 2.6.0-test2-mm2 fixed any
> >   PS/2 or synaptics problems.  You are all very bad.
> 
> Will report 12 hours from now or so, I have synaptics problems currently.
> 
> > -selinux.patch
> (...)
> >  merged
> 
> Sure about this?

yes.

> > +4g-2.6.0-test2-mm2-A5.patch
> > 
> >  4G/4G split
> 
> Linus called this patch 'tasteless' - do you see this being merged?

Bolting 64G of memory onto a 32-bit CPU is tasteless too...

We already have a bucketload of highmem hacks in the kernel, and they are
not sufficient for some people.  We have several more (large) highmem hacks
being proposed.

It is fairly clear that a number of users will need more highmem hacks than
we currenly have.  I'd rather add one more big highmem hack than a whole
bunch more little ones.  And I'd rather that the big highmem hack be in the
base kernel, rather than having different versions floating about in
different vendor trees.

It seems that 4G+4G is the most viable patch at this stage.  Wider testing
will tell.

I rather wish that the patch had been available a year ago, so we would now
have less little highmem hacks in the tree.

wrt long-term kernel purity: one approach would be to not merge 4G+4G into
2.7 at all.  This keeps the long-term kernel codebase saner.  It assumes
that the monster 32-bit boxes will have been obsoleted by 64-bit machines
within 3-4 years and that it is acceptable to end-of-line those machines on
a 2.6-based kernel.  I think that's pretty safe.


The main concern is that I don't want to see vendor kernels madly diverging
from the public kernel right at the outset of the 2.6 series.


  reply	other threads:[~2003-08-02 23:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-02 22:22 2.6.0-test2-mm3 Andrew Morton
2003-08-02 22:31 ` 2.6.0-test2-mm3 bert hubert
2003-08-02 23:42   ` Andrew Morton [this message]
2003-08-03  7:38     ` 2.6.0-test2-mm3 William Lee Irwin III
2003-08-04 12:10     ` 2.6.0-test2-mm3 jlnance
2003-08-03  0:11 ` 2.6.0-test2-mm3 William Lee Irwin III
2003-08-03  2:14   ` 2.6.0-test2-mm3 William Lee Irwin III
2003-08-03  1:49 ` 2.6.0-test2-mm3 Felipe Alfaro Solana
2003-08-03  2:00   ` 2.6.0-test2-mm3 Andrew Morton
2003-08-03  2:03     ` 2.6.0-test2-mm3 Felipe Alfaro Solana
2003-08-03  5:07 ` 2.6.0-test2-mm3 Zwane Mwaikambo
2003-08-03  5:28   ` 2.6.0-test2-mm3 Andrew Morton
2003-08-03  5:22     ` 2.6.0-test2-mm3 Zwane Mwaikambo
2003-08-03  5:38       ` 2.6.0-test2-mm3 Joshua Kwan
2003-08-03  5:48       ` 2.6.0-test2-mm3 Zwane Mwaikambo
2003-08-03  7:05 ` 2.6.0-test2-mm3 Danek Duvall
2003-08-03  7:15   ` 2.6.0-test2-mm3 Eugene Teo
2003-08-03  7:28     ` 2.6.0-test2-mm3 Danek Duvall
2003-08-03  7:44       ` 2.6.0-test2-mm3 Eugene Teo
2003-08-03  2:57 2.6.0-test2-mm3 Raphael Kubo da Costa
2003-08-03 10:36 ` 2.6.0-test2-mm3 Jose Luis Domingo Lopez
2003-08-03 15:13   ` 2.6.0-test2-mm3 Marcelo Abreu
2003-08-03 15:59     ` 2.6.0-test2-mm3 Ingo Molnar

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=20030802164205.5cc42edc.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ahu@ds9a.nl \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).