From: "michael chang" <thenewme91@gmail.com>
To: "Con Kolivas" <kernel@kolivas.org>
Cc: "ck mailing list" <ck@vds.kolivas.org>,
"linux kernel mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: [ck] Re: 2.6.20-ck1
Date: Fri, 16 Feb 2007 21:15:25 -0500 [thread overview]
Message-ID: <b14e81f00702161815x13c25936r49f540beeda3e334@mail.gmail.com> (raw)
In-Reply-To: <200702171213.40718.kernel@kolivas.org>
On 2/16/07, Con Kolivas <kernel@kolivas.org> wrote:
> I'm thru with bashing my head against the wall.
I do hope this post isn't in any way redundant, but from what I can
see, this has never been suggested... (someone please do enlighten me
if I'm wrong.)
Has anyone tried booting a kernel with the various patches in question
with a mem=###M boot flag (maybe mem=96M or some other "insanely low
number" ?) to make the kernel think it has less memory than is
physically available (and then compare to vanilla with the same
flags)? It might more clearly demonstrate the effects of Con's patches
when the kernel thinks (or knows) it has relatively little memory
(since many critics, from what I can tell, have quite a bit of memory
on their systems for their workloads).
Just my two cents.
--
~Mike
- Just the crazy copy cat.
next prev parent reply other threads:[~2007-02-17 2:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 10:10 2.6.20-ck1 Con Kolivas
2007-02-16 15:47 ` 2.6.20-ck1 Malte Schröder
2007-02-16 21:35 ` 2.6.20-ck1 Edouard Gomez
2007-02-16 21:45 ` 2.6.20-ck1 Edouard Gomez
2007-02-17 0:53 ` 2.6.20-ck1 Chuck Ebbert
2007-02-17 1:13 ` 2.6.20-ck1 Con Kolivas
2007-02-17 2:15 ` michael chang [this message]
2007-02-17 3:17 ` [ck] 2.6.20-ck1 Con Kolivas
2007-02-17 17:28 ` michael chang
2007-02-17 18:45 ` Chuck Ebbert
2007-02-17 21:00 ` Con Kolivas
2007-02-17 21:50 ` michael chang
2007-02-17 23:47 ` Andrew Morton
2007-02-18 0:39 ` 2.6.20-ck1 Con Kolivas
2007-02-18 0:41 ` [ck] 2.6.20-ck1 Radoslaw Szkodzinski
2007-02-18 0:45 ` 2.6.20-ck1 Con Kolivas
2007-02-17 11:15 ` 2.6.20-ck1 Hugo Vanwoerkom
2007-02-18 2:14 ` 2.6.20-ck1 mdew .
2007-02-18 2:38 ` 2.6.20-ck1 Con Kolivas
2007-02-18 6:05 ` [ck] 2.6.20-ck1 Con Kolivas
2007-02-18 6:15 ` Rodney Gordon II
2007-02-18 6:20 ` Rodney Gordon II
2007-02-18 16:54 ` 2.6.20-ck1 Ryan M.
2007-02-18 19:00 ` [ck] 2.6.20-ck1 Ash Milsted
2007-02-24 12:12 ` 2.6.20-ck1 Fabio Comolli
2007-02-25 4:34 ` 2.6.20-ck1 Gene Heskett
2007-02-25 10:32 ` 2.6.20-ck1 Con Kolivas
2007-02-25 16:33 ` 2.6.20-ck1 Gene Heskett
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=b14e81f00702161815x13c25936r49f540beeda3e334@mail.gmail.com \
--to=thenewme91@gmail.com \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.org \
--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
all inboxes | Powered by JetHome®