mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "Marcos D. Marado Torres" <marado@student.dei.uc.pt>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	lse-tech <lse-tech@lists.sourceforge.net>
Subject: Re: 2.6.0-mjb1
Date: Thu, 25 Dec 2003 12:52:09 -0800	[thread overview]
Message-ID: <175850000.1072385528@[10.10.2.4]> (raw)
In-Reply-To: <Pine.LNX.4.58.0312252019070.23168@student.dei.uc.pt>

>> I'd be very interested in feedback from anyone willing to test on any
>> platform, however large or small.
> 
> It's working perfectly for me: in fact it's what I'm running right now.
> I'm running it on an Asus M3700N laptop...
> Any tests you want me to do, just e-mail asking them.

Cool - thanks. It probably doesn't get as much testing under memory 
pressure as it should on laptop-sized systems (though I do my best on
my own boxes). I'd be interested to see how it performs for people on 
desktop/laptops compared to virgin 2.6.0 - objrmap pays a little during
pageout for what it gains during regular usage. Just regular desktop
workload stuff, but measuring performance can be somewhat subjective
unless you have a more formal (and artificial) test. As long as it's
tangibly worse, that's fine.

Or if people are bored, and want something functional to test ... ;-) 
Fiddle with some of the new config options, eg turn on 4/4 split or 
2/2 split, or HZ=100, kgdb, kcg, schedstat, etc. Early printk is 
interesting too, but harder to test - you really need to make it
lock up before console_init somehow (adding a BUG() or something).

Thanks,

M.


      reply	other threads:[~2003-12-25 20:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-25 16:35 2.6.0-mjb1 Martin J. Bligh
2003-12-25 20:22 ` 2.6.0-mjb1 Marcos D. Marado Torres
2003-12-25 20:52   ` Martin J. Bligh [this message]

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='175850000.1072385528@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=marado@student.dei.uc.pt \
    /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®