public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Ed Sweetman <ed.sweetman@wmich.edu>,
	Mike Fedyk <mfedyk@matchmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Nick's scheduler policy v12
Date: Sun, 07 Sep 2003 14:42:04 +1000	[thread overview]
Message-ID: <3F5AB71C.5060904@cyberone.com.au> (raw)
In-Reply-To: <146640000.1062902095@[10.10.2.4]>



Martin J. Bligh wrote:

>>All of this basing scheduling performance on a bloated wannabe winamp 
>>makes as much sense as gauging car performance using a van.   If this 
>>was a purely scheduling problem, then why do other players like 
>>alsaplayer and such not suck as bad as xmms when under the exact same 
>>priority and all?  At least use something without a frontend so that 
>>you can limit the possibility that the programmers did something stupid 
>>like make decoding dependent on some update to the gui. 
>>xmms was coded first and foremost to look and work like winamp. 
>>Streamlined - even low latency performance was not a base goal.  
>>
>
>The reality is that people use xmms, and whilst it may not be the greatest
>program known to man, I don't believe it's *that* fundamentally screwed up
>that it should skip under normal desktop loads. *Especially* if it worked
>fine under 2.4 ;-)
>

I agree with Martin here. xmms may not be the smartest music player,
but its really sad if it skips on a P4 or Athlon.



  parent reply	other threads:[~2003-09-07  4:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-05 17:57 [PATCH] Nick's scheduler policy v12 Nick Piggin
2003-09-05 18:54 ` Martin J. Bligh
2003-09-05 20:22   ` Mike Fedyk
2003-09-05 20:19     ` Martin J. Bligh
2003-09-05 20:39       ` Mike Fedyk
2003-09-05 21:08         ` Robert Love
2003-09-06  1:31           ` Nick Piggin
2003-09-06  1:18       ` Nick Piggin
2003-09-06  3:36         ` Martin J. Bligh
2003-09-06  6:20           ` Jörn Engel
2003-09-06  6:38           ` Nick Piggin
2003-09-06  6:55             ` Nick Piggin
2003-09-06 15:13             ` Martin J. Bligh
2003-09-06 11:47               ` Ed Sweetman
2003-09-07  2:34                 ` Martin J. Bligh
2003-09-07  3:27                   ` Valdis.Kletnieks
2003-09-07  4:42                   ` Nick Piggin [this message]
2003-09-07  4:37               ` Nick Piggin
2003-09-06  7:49           ` Martin Schlemmer

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=3F5AB71C.5060904@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=ed.sweetman@wmich.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=mfedyk@matchmail.com \
    /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