From: Jeff Garzik <jgarzik@pobox.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>,
Linus Torvalds <torvalds@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.7-rc1
Date: Sun, 23 May 2004 18:19:56 -0400 [thread overview]
Message-ID: <40B1238C.6060605@pobox.com> (raw)
In-Reply-To: <20040523215330.GG1833@holomorphy.com>
William Lee Irwin III wrote:
> William Lee Irwin III wrote:
>
>>>I wouldn't qualify either of the major VM patch series merged as
>>>rewrites. I saw:
>>>(1) move unmapping function/helpers to different algorithm to save space
>>>(2) NUMA API and support functions
>
>
> On Sun, May 23, 2004 at 05:30:55PM -0400, Jeff Garzik wrote:
>
>>You missed the pte chains going away, a fundamental change in the way
>>reverse mapping is done?
>
>
> (1) describes that in more detail than "pte_chains going away". It's
> just a search algorithm. For anonymous pages, anon_vma just strobes
> offsets into vma inheritance chains, and anonmm just strobes vaddrs in
> all forks between execs, for file-backed memory they both use ->i_mmap.
> Yes, they can both be summarized in the same sentence. The scope of the
> changes are very limited and the presentation of them is a very clearly
> documented and incremental series of small changes.
You're getting lost in the details... the scope of the anonvma change
is _everybody_. If you accept the premise that we are in a _stable_
kernel series, the core goal should be stability. Non-trivial VM
changes like this do not enhance stability in the short term, even if
they are a good idea in the long run. It's the whole idea behind
minimizing changes and breakage in a stable series.
You've got all the major Linux vendors preparing (or releasing)
2.6.x-based product and IMO the 2.6 kernel is still a moving target,
with non-trivial behavior (and sometimes API) changes every couple of
kernel versions.
Jeff
next prev parent reply other threads:[~2004-05-23 22:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-23 6:38 Linux 2.6.7-rc1 Linus Torvalds
2004-05-23 8:12 ` Michael Neuffer
2004-05-23 16:19 ` Horst von Brand
2004-05-23 18:33 ` Jeff Garzik
2004-05-23 21:11 ` William Lee Irwin III
2004-05-23 21:30 ` Jeff Garzik
2004-05-23 21:53 ` William Lee Irwin III
2004-05-23 22:19 ` Jeff Garzik [this message]
2004-05-24 1:56 ` Linus Torvalds
2004-05-24 0:25 ` Linux 2.6.7-rc1 - drivers/scsi/ipr.h too smart for me Eyal Lebedinsky
2004-05-24 22:12 ` Linux 2.6.7-rc1 (compile stats) John Cherry
[not found] <20040523173738.GY23361@viasys.com>
2004-05-23 22:58 ` Linux 2.6.7-rc1 Horst von Brand
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=40B1238C.6060605@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=vonbrand@inf.utfsm.cl \
--cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox