From: William Lee Irwin III <wli@holomorphy.com>
To: Jeff Garzik <jgarzik@pobox.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 14:11:54 -0700 [thread overview]
Message-ID: <20040523211154.GC1833@holomorphy.com> (raw)
In-Reply-To: <40B0EE6C.70400@pobox.com>
On Sun, May 23, 2004 at 02:33:16PM -0400, Jeff Garzik wrote:
> Linux has a tradition of completely rewriting the VM in the middle of a
> stable series, why not again? :)
> /me is joking, but similarly annoyed...
> The VM, like the rest of the kernel, will _always_ be a work in
> progress. A stable series should freeze us for bug fixing and
> stabilization...
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
At the risk of trivializing the large amount of work that went into
minimizing the risk of merging these things, the VM hasn't been changed
in any fundamental way by either of them.
-- wli
next prev parent reply other threads:[~2004-05-23 21:15 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 [this message]
2004-05-23 21:30 ` Jeff Garzik
2004-05-23 21:53 ` William Lee Irwin III
2004-05-23 22:19 ` Jeff Garzik
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=20040523211154.GC1833@holomorphy.com \
--to=wli@holomorphy.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=vonbrand@inf.utfsm.cl \
/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