public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	David Newall <davidn@davidnewall.com>,
	Mike Galbraith <efault@gmx.de>, Al Viro <viro@zeniv.linux.org.uk>,
	"J.C. Pizarro" <jcpiza@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: linux+glibc memory allocator, poor performance
Date: Fri, 14 Mar 2008 07:05:30 +0100	[thread overview]
Message-ID: <20080314060529.GK8953@1wt.eu> (raw)
In-Reply-To: <84144f020803130548o76f80fedm378f82e95c189ce2@mail.gmail.com>

On Thu, Mar 13, 2008 at 02:48:31PM +0200, Pekka Enberg wrote:
> Hi Alan,
> 
> On Thu, Mar 13, 2008 at 2:10 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> >  I think it would be far better to create linux-flame and send the hostile
> >  stuff away. In a lot of cultures hostile responses or unfriendly
> >  responses are taken badly. Politeness is a good thing this list needs
> >  more of.
> 
> Do you honestly think we should be polite to people trolling on the
> LKML? The problem with kill-filing people like J.C. Pizzarro (a known
> troll on the GCC mailing list at least) is that other people will
> engange in discussing these "proposals" and contribute in generating
> noise anyway.

Being polite, understanding and grateful generally encourages people
to contribute and progress. Being sometimes rude helps them understand
they went too far, and gives more credit to your politeness in normal
time because you're seen as balanced. Being always rude or always
excessively polite just assigns you a style by which people don't know
what you really think. So using all the capabilities of the language
is finally the best solution to precisely express what you think.

Willy


  parent reply	other threads:[~2008-03-14  6:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 20:09 linux+glibc memory allocator, poor performance J.C. Pizarro
2008-03-12 21:12 ` Al Viro
2008-03-13  5:57   ` David Newall
2008-03-13  6:12     ` Mike Galbraith
2008-03-13  6:22       ` David Newall
2008-03-13  7:38         ` Christoph Hellwig
2008-03-13 11:02           ` David Newall
2008-03-13  9:10         ` Pekka Enberg
2008-03-13 11:04           ` David Newall
2008-03-13 12:10           ` Alan Cox
2008-03-13 12:48             ` Pekka Enberg
2008-03-13 13:55               ` J.C. Pizarro
2008-03-13 19:40               ` David Newall
2008-03-13 20:05                 ` Pekka Enberg
2008-03-13 22:50                 ` Al Viro
2008-03-14 12:11                   ` Stephen Clark
2008-03-14  6:05               ` Willy Tarreau [this message]
2008-03-13 10:50     ` David Newall
2008-03-13 12:23   ` J.C. Pizarro
2008-03-12 21:22 ` Rik van Riel
2008-03-12 21:32   ` Al Viro
  -- strict thread matches above, loose matches on Subject: below --
2008-03-12 18:14 Xose Vazquez Perez
2008-03-17 18:36 ` Xose Vazquez Perez

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=20080314060529.GK8953@1wt.eu \
    --to=w@1wt.eu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davidn@davidnewall.com \
    --cc=efault@gmx.de \
    --cc=jcpiza@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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