public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wiktor Wodecki <wodecki@gmx.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]O18int
Date: Fri, 22 Aug 2003 16:56:23 +0200	[thread overview]
Message-ID: <20030822145622.GA716@gmx.de> (raw)
In-Reply-To: <200308222351.16691.kernel@kolivas.org>

[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]

On Fri, Aug 22, 2003 at 11:51:16PM +1000, Con Kolivas wrote:
> On Friday 22 August 2003 23:41, Wiktor Wodecki wrote:
> > On Fri, Aug 22, 2003 at 10:31:20PM +1000, Con Kolivas wrote:
> > Content-Description: clearsigned data
> >
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Here is a small patchlet.
> > >
> > > It is possible tasks were getting more sleep_avg credit on requeuing than
> > > they could burn off while running so I've removed the on runqueue bonus
> > > to requeuing task.
> > >
> > > Note this applies onto O16.3 or 2.6.0-test3-mm3 as O17 was dropped.
> > >
> > > This patch is also available here along with a patch against 2.6.0-test3:
> > > http://kernel.kolivas.org/2.5
> > >
> > > Con
> >
> > this patch still makes my xmms skip on light io load (untar kernel
> > source, open lkml mailbox folder) while opening mozilla. Even after
> > mozilla is there xmms is still skipping. Processes take ages to spawn.
> > And no, I'm not in swap. A 'su -'is taking 10 seconds to procceed.
> > Same applies when rm -Rf'ing a kernel tree.
> > Here is some more data for the curious:
> 
> > note the load of 11. I can even get it to 30 while doing 3 tar xf
> > bla.tar simultanously.
> 
> Complete mystery.
> >
> > I'm going to fetch some fish in the next two weeks in poland, so I will
> > not be able to do any more testing from sunday on. Happy coding (while I
> > stick to O10 *g*)
> 
> Thanks for comments. ]
> 
> There it is again; the reference to darn O10. Hrm. One question before your 
> holiday; your O10 kernel is it the same kernel tree or a different/newere 
> one? I'm looking to blame something else here I know but I need to know; this 
> just doesn't hold with any testing here.

well, I run O10 on top of test2, since I didn't need any patches from
test3 I didn't rediff it.

-- 
Regards,

Wiktor Wodecki

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-22 14:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-22 12:31 [PATCH]O18int Con Kolivas
2003-08-22 13:41 ` [PATCH]O18int Wiktor Wodecki
2003-08-22 13:51   ` [PATCH]O18int Con Kolivas
2003-08-22 14:56     ` Wiktor Wodecki [this message]
     [not found]       ` <200308230103.19724.kernel@kolivas.org>
2003-08-22 15:46         ` [PATCH]O18int Wiktor Wodecki
2003-08-22 15:54           ` [PATCH]O18int Con Kolivas
2003-08-22 17:53   ` [PATCH]O18int Mike Fedyk
     [not found]     ` <200308222335.50318.insecure@mail.od.ua>
2003-08-22 20:44       ` [PATCH]O18int Wiktor Wodecki
2003-08-22 21:04         ` [PATCH]O18int Mike Fedyk
2003-08-22 22:40 ` [PATCH]O18int Felipe Alfaro Solana
2003-08-27 23:02   ` [PATCH]O18int Wes Janzen

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=20030822145622.GA716@gmx.de \
    --to=wodecki@gmx.de \
    --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