linux-kernel - Re: linux+glibc memory allocator, poor performance

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080313225040.GO27894@ZenIV.linux.org.uk>
Date:	Thu, 13 Mar 2008 22:50:40 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	David Newall <davidn@...idnewall.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: linux+glibc memory allocator, poor performance

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@...rguk.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/