From: Stephen Clark <Stephen.Clark@seclark.us>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: David Newall <davidn@davidnewall.com>, linux-kernel@vger.kernel.org
Subject: Re: linux+glibc memory allocator, poor performance
Date: Fri, 14 Mar 2008 08:11:14 -0400 [thread overview]
Message-ID: <47DA6B62.5080103@seclark.us> (raw)
In-Reply-To: <20080313225040.GO27894@ZenIV.linux.org.uk>
Al Viro wrote:
> On Fri, Mar 14, 2008 at 06:10:01AM +1030, David Newall wrote:
>
>> Pekka Enberg wrote:
>>
>>> Hi Alan,
>>>
>>> On Thu, Mar 13, 2008 at 2:10 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>>>
>>>
>>>> Politeness is a good thing this list needs more of.
>>>>
>>>>
>>> Do you honestly think we should be polite to people trolling on the
>>> LKML?
>>>
>> I do. It's obvious. Rudeness detracts (and reflects poorly on one's
>> parents.) Good manners cost nothing. I might also point out that it
>> was bad manners, not any alleged trolling, which caused this sad
>> discussion.
>>
>
> "Deliberate insult" would describe the original posting more accurately.
> Whether you prefer to look at it as a show of bad manners or as trolling
> is a matter of perspective; arguably it had been both.
>
>
>> Don't be rude; rather say nothing.
>>
>
> Request duly noted and denied. For the record: condescending twits of that
> variety ("I can't be arsed to look at code I'm commenting on; here's my
> valuable insight that is obviously beyond the mental capacity of anybody
> here") can expect a harsh reply, whoever they are. I'm yet to see l-k
> regulars treating newbies that way, BTW, despite the much decried lack of
> politeness.
>
> Since you are postulating social norms, here's one you seem to have overlooked:
> one who comments on code or design, be it review, suggestions of changes/
> improvements, etc., ought to read the thing he is commenting on. Whoever
> it is and wherever the code in question might be. And yes, it applies to
> kernel hackers commenting on newbies' patches to the same extent as to
> completely unknown folks commenting on the kernel, etc.
>
> Breaking that rule and being caught at that is one hell of a way to earn
> yourself a lousy reputation. Combine that with arrogance and... well,
> there's a term for what you become: target practice.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
Someone once said:
"If you don't have anything good to say, don't day anything at all".
I have been reading LKML since the mid 90's and continually see people
jump on
what are maybe dumb/stupid questions or trolls instead of simply
ignoring them.
My $.02
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
next prev parent reply other threads:[~2008-03-14 12:11 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 [this message]
2008-03-14 6:05 ` Willy Tarreau
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=47DA6B62.5080103@seclark.us \
--to=stephen.clark@seclark.us \
--cc=davidn@davidnewall.com \
--cc=linux-kernel@vger.kernel.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