From: Austin Gonyou <austin@digitalroadkill.net>
To: anton wilson <anton.wilson@camotion.com>
Cc: J Sloan <jjs@lexus.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4 O(1) scheduler
Date: 19 Jul 2002 15:46:27 -0500 [thread overview]
Message-ID: <1027111587.6685.24.camel@UberGeek> (raw)
In-Reply-To: <200207192018.QAA19141@test-area.com>
Been using 2.4.19-rc1-aa2 on a fairly large x86 box for about 16 days
now. Nothing but love. Using the 0/1 scheduler, though I'm not sure if I
could tweak it for "better" performance.(hint: like to see some
"best-practices" type of doc, for 4/8-way SMP boxen)
Aside from that, I've got 8GB ram, a ~750GB Oracle instance running, and
4GB SHMMAX attatched to some Copper FC1 disks and using QLA2200's.
It's been very happy since rc1. Anyway, it's worth a shot. As soon as
2.4.19 is "done" this box will go into production as soon as this RC2 VM
stuff is cleared up.
On Fri, 2002-07-19 at 15:17, anton wilson wrote:
> On Friday 19 July 2002 03:54 pm, J Sloan wrote:
> > Use 2.4-aa, 2.4-ac or 2.4-redhat kernel
> > and you get the O(1) secheduler at
> > no extra cost -
> >
>
>
> > Joe
>
>
> I'm actually worried not about just the O(1) scheduler but if these patches
> will be incorporating the O(1) bug fixes such as the serious one in
> balance_load where curr->next was used instead of current->prev. Also, I need
> to use a patch that won't tamper with the usb implementation because I'd have
> to update our current usb driver to fit into the new system, and I'm getting
> flack about wasting time trying to update that thing already . . . So if you
> tell me no, I can go tell my boss I have to update the usb driver.
>
>
> Anton
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Austin Gonyou <austin@digitalroadkill.net>
next prev parent reply other threads:[~2002-07-19 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 19:42 2.4 O(1) scheduler anton wilson
2002-07-19 19:54 ` J Sloan
2002-07-19 20:17 ` anton wilson
2002-07-19 20:46 ` Austin Gonyou [this message]
2002-07-19 21:42 ` J Sloan
2002-07-21 6:47 ` Ingo Molnar
2002-07-21 14:26 ` 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=1027111587.6685.24.camel@UberGeek \
--to=austin@digitalroadkill.net \
--cc=anton.wilson@camotion.com \
--cc=jjs@lexus.com \
--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