public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Carlo Florendo <subscribermail@gmail.com>
Cc: "Lenar Lõhmus" <lenar@city.ee>,
	"Klaus Schulz" <Klaus.Schulz@web.de>,
	ck@vds.kolivas.org, linux-kernel@vger.kernel.org,
	"Martin Steigerwald" <Martin@lichtvoll.de>
Subject: Re: ck vs. cfs : realtime audio performance
Date: Thu, 2 Aug 2007 21:26:25 +0200	[thread overview]
Message-ID: <20070802192625.GA17944@elte.hu> (raw)
In-Reply-To: <46B17937.1050401@gmail.com>


* Carlo Florendo <subscribermail@gmail.com> wrote:

>>>> With CFS I also experienced XRUNS from time to time, what never 
>>>> happened with ck.
> 
> See, this is exactly the problem of the SD ranters.  A ranter posts a 
> problem, doesn't give reproducability hints, and neither provides 
> technical detail, not even the slightest relevant stats.  And the most 
> irritating part is that the code that the OP wrote (or at least its 
> relevant parts) is not even available for download.

actually, there was no "SD ranting" going on at all. Klaus reported a 
problem, Martin forwarded it to me, i replied to it and Klaus gave me 
lots of debug info in a very professional way. So please calm down and 
lets get back to the tech topics, ok? (and i'd like to apologize here to 
Karl and Martin for the rough and unjust treatment they received on 
lkml.)

	Ingo

  reply	other threads:[~2007-08-02 19:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1185870355.7933.55.camel@klaus-laptop>
     [not found] ` <1185886161.7397.11.camel@klaus-laptop>
2007-07-31 12:54   ` ck vs. cfs : realtime audio performance Lenar Lõhmus
2007-08-01  6:31     ` Ingo Molnar
2007-08-02  6:27     ` Carlo Florendo
2007-08-02 19:26       ` Ingo Molnar [this message]
2007-08-02  7:57 Klaus Schulz
2007-08-02  9:06 ` Carlo Florendo

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=20070802192625.GA17944@elte.hu \
    --to=mingo@elte.hu \
    --cc=Klaus.Schulz@web.de \
    --cc=Martin@lichtvoll.de \
    --cc=ck@vds.kolivas.org \
    --cc=lenar@city.ee \
    --cc=linux-kernel@vger.kernel.org \
    --cc=subscribermail@gmail.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