public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: Roman Zippel <zippel@linux-m68k.org>, Ingo Molnar <mingo@elte.hu>,
	Rob Hussey <robjhussey@gmail.com>,
	efault@gmx.de, a.p.zijlstra@chello.nl,
	linux-kernel@vger.kernel.org, ck@vds.kolivas.org
Subject: Re: Scheduler benchmarks - a follow-up
Date: Mon, 17 Sep 2007 22:42:27 +0200	[thread overview]
Message-ID: <20070917204227.GA20620@1wt.eu> (raw)
In-Reply-To: <20070917200639.GA24301@flower.upol.cz>

On Mon, Sep 17, 2007 at 10:06:40PM +0200, Oleg Verych wrote:
> On Mon, Sep 17, 2007 at 09:43:42PM +0200, Willy Tarreau wrote:
> > 
> > On Mon, Sep 17, 2007 at 09:45:59PM +0200, Oleg Verych wrote:
> > > The copy list, removed by Ingo is restored. Playing fair game, Willy!
> > 
> > Sorry Oleg, I don't understand why you added me to this thread. And I
> > don't understand at all what your intent was :-/
> > 
> > I've left others Cc too since they wonder like me.
> 
> Why? Answer: <http://mid.gmane.org/20070913230836.GA16536@1wt.eu>
> 
> IMHO you shouldn't leave public lists in the reply like this. Whatever.

Nothing prevents Roman and I to exchange our respective points of views
on LKML when those are about other activities on the list, I don't get
your point.

I find particularly weird the way you hijacked an existing thread
adding references to a 4-days old mail and adding people in Cc just
as one would add fuel to try to start any sort of flamewar.

Sorry for you, but this has no chance to succeed. First, don't consider
that people are ennemies just because they use harsh words to tell each
other what they feel about a specific subject (otherwise, you'd find
hundreds of ennemies of everyone here). Second, if there are some aspects
of the mail above that you want explained, you can mail us privately,
you're not necessarily forced to hijack an unrelated discussion.

Now I'm not interested in following up into this thread, it's already
polluted. Please let people here discuss numbers and experiments.

Thanks,
Willy


  parent reply	other threads:[~2007-09-17 20:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-17  9:21 Scheduler benchmarks - a follow-up Rob Hussey
2007-09-17 11:12 ` Ed Tomlinson
2007-09-17 11:47   ` Ingo Molnar
2007-09-17 20:22   ` Ingo Molnar
2007-09-17 11:27 ` Ingo Molnar
     [not found]   ` <E1IXMXf-0000uG-ID@flower>
2007-09-17 19:43     ` Willy Tarreau
2007-09-17 20:01       ` Ingo Molnar
2007-09-17 20:06       ` Oleg Verych
2007-09-17 20:05         ` Ingo Molnar
2007-09-17 20:42         ` Willy Tarreau [this message]
2007-09-17 13:05 ` Ingo Molnar
2007-09-17 14:01   ` [ck] " Jos Poortvliet
2007-09-17 14:12     ` Ingo Molnar
2007-09-17 20:36   ` Ingo Molnar
2007-09-18  4:30     ` Rob Hussey
2007-09-18  4:53       ` Willy Tarreau
2007-09-18  4:58         ` Rob Hussey
2007-09-18  6:40       ` Ingo Molnar
2007-09-18  8:23         ` Rob Hussey
2007-09-18  8:48       ` Ingo Molnar
2007-09-18  9:45         ` Rob Hussey
2007-09-18  9:48           ` Ingo Molnar
2007-09-18  1:44   ` Rob Hussey

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=20070917204227.GA20620@1wt.eu \
    --to=w@1wt.eu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=ck@vds.kolivas.org \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=olecom@flower.upol.cz \
    --cc=robjhussey@gmail.com \
    --cc=zippel@linux-m68k.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