public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
	prakashpublic@gmx.de, linux-kernel@vger.kernel.org
Subject: Re: Terrible interactivity with 2.6.0-t9-mm3
Date: Mon, 17 Nov 2003 09:18:41 +1100	[thread overview]
Message-ID: <20031116221840.GA524@zip.com.au> (raw)
In-Reply-To: <20031116141342.54a79e32.akpm@osdl.org>

On Sun, Nov 16, 2003 at 02:13:42PM -0800, Andrew Morton wrote:
> Arnaldo Carvalho de Melo <acme@conectiva.com.br> wrote:
> > Em Sun, Nov 16, 2003 at 01:42:31PM -0800, Andrew Morton escreveu:
> > > "Prakash K. Cheemplavam" <prakashpublic@gmx.de> wrote:
> > > > CaT wrote:
> > > > 
> > > >  > I just noticed major interactivity problems whilst ogging one of my
> > > 
> > > "ogging"?
> > 
> > To Ogg: to oggify, to convert some digital sound file to the .ogg format
> 
> This much I know.  But it's not exactly a tightly defined and repeatable
> workload.  Oh well.

I can't do much testing atm but the similar symptoms happen whilst running
Heroes3 which tends to suck CPU so I think mp3 encoding would work just 
aswell or anything else that sucks all the CPU it can.

Prakash also reported similar problems whilst compiling the kernel. This is
something I can duplicate also. As my kernel compiles the system can't
even keep up with my typing.

-- 
  From the people who brought you burnt villages in Vietnam...

      http://news.independent.co.uk/world/middle_east/story.jsp?story=452375

  reply	other threads:[~2003-11-16 22:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-16 19:26 Terrible interactivity with 2.6.0-t9-mm3 CaT
2003-11-16 20:24 ` Prakash K. Cheemplavam
2003-11-16 21:42   ` Andrew Morton
2003-11-16 22:06     ` Arnaldo Carvalho de Melo
2003-11-16 22:13       ` Andrew Morton
2003-11-16 22:18         ` CaT [this message]
2003-11-17  0:16     ` Panagiotis Papadakos
2003-11-17  2:20     ` Gawain Lynch
2003-11-17  2:49       ` Andrew Morton
2003-11-17  3:11         ` Gawain Lynch
2003-11-17  3:54         ` Gene Heskett
2003-11-17  4:19           ` Nick Piggin
2003-11-17  4:47             ` Gene Heskett
2003-11-17  5:17               ` Nick Piggin
  -- strict thread matches above, loose matches on Subject: below --
2003-11-17 12:11 Ronny V. Vindenes
2003-11-17 13:12 ` Prakash K. Cheemplavam
2003-11-17 19:46   ` Thomas Schlichter
2003-11-17 21:27     ` john stultz
2003-11-17 22:44       ` john stultz
2003-11-17 22:51       ` Prakash K. Cheemplavam
2003-11-17 22:55         ` john stultz
2003-11-17 23:04           ` john stultz
2003-11-17 23:46             ` Thomas Schlichter
2003-11-18 13:24             ` Prakash K. Cheemplavam
2003-11-18 16:11               ` Prakash K. Cheemplavam
2003-11-18 18:28                 ` john stultz
2003-11-18 16:15               ` Prakash K. Cheemplavam
2003-11-17 13:15 ` Felipe Alfaro Solana
2003-11-17 19:36 ` Andrew Morton
2003-11-17 19:35   ` john stultz
2003-11-18 18:56   ` Dominik Brodowski
2003-11-18 19:18     ` john stultz

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=20031116221840.GA524@zip.com.au \
    --to=cat@zip.com.au \
    --cc=acme@conectiva.com.br \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prakashpublic@gmx.de \
    /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