linux-kernel - Re: [PATCH UPDATED] percpu: use dynamic percpu allocator as the default percpu allocator

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: <20090414140416.GE27163@elte.hu>
Date:	Tue, 14 Apr 2009 16:04:16 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Christoph Lameter <cl@...ux.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Tejun Heo <tj@...nel.org>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	rusty@...tcorp.com.au, tglx@...utronix.de, x86@...nel.org,
	linux-kernel@...r.kernel.org, hpa@...or.com,
	Paul Mundt <lethal@...ux-sh.org>, rmk@....linux.org.uk,
	starvik@...s.com, ralf@...ux-mips.org, davem@...emloft.net,
	cooloney@...nel.org, kyle@...artin.ca, matthew@....cx,
	grundler@...isc-linux.org, takata@...ux-m32r.org,
	benh@...nel.crashing.org, rth@...ddle.net,
	ink@...assic.park.msu.ru, heiko.carstens@...ibm.com,
	Nick Piggin <npiggin@...e.de>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH UPDATED] percpu: use dynamic percpu allocator as the
	default percpu allocator

* Christoph Lameter <cl@...ux.com> wrote:

> On Wed, 8 Apr 2009, Ingo Molnar wrote:
> 
> > Dude, this is a new facility freshly modernized and freshly made
> > usable. What did you expect, for a thousand usecases pop up in the
> > kernel overnight? _None_ of this code is "common" today per se. (the
> > networking folks are working on making it more and more common
> > though)
> 
> ?? kfree(NULL) has been allowed for years. None of this is new.

[ This reply if yours is completely inapposite. It does not fit into 
  the logical stream of arguments at all. Of course kfree(NULL) has 
  been allowed for years. Did i claim otherwise? I dont think you
  understand my arguments - and i get the impression that you dont
  even _try_ to understand them. ]

The thing is, i spent well in excess of an hour analyzing your 
patch, counting cachelines, looking at effects and interactions, 
thinking about the various implications. I came up with a good deal 
of factoids, a handful of suggestions and a few summary paragraphs:

  http://marc.info/?l=linux-kernel&m=123862536011780&w=2

A proper reply to that work would be one of several responses:

  1) to ignore it. (you can always do that, you dont have to react
     to everything on lkml - especially if you think it's bull.)

  2) disagree with the factoids - preferably in a specific way.

  3) agree with the factoids and disagree with my opinion.

  4) agree with it all.

You did neither of these: you never replied to my detailed analysis, 
you only replied to my followup summary - disagreeing with my 
opinion based not on a fair deconstruction of my factoids but on a 
mere repetition of your arguments.

Furthermore, you also tried to 'win' this argument by increasing the 
volume of shouting, by injecting unprovoked insults and by using a 
patronizing and irritated tone.

You might be completely right in the end technically (i fully submit 
that the discussion is open-ended), but this kind of generic 
handwaving and your asocial behavior in this thread does not really 
do your technical arguments any service. It can only really end in 
me starting to ignore you.

	Ingo
--
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/