From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Tejun Heo <tj@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
kyle@mcmartin.ca
Subject: Re: [GIT PULL] percpu for 2.6.31
Date: Fri, 19 Jun 2009 12:39:18 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906191235490.16802@localhost.localdomain> (raw)
In-Reply-To: <20090619053944.GB8162@elte.hu>
On Fri, 19 Jun 2009, Ingo Molnar wrote:
>
> ( Many wont btw: we still dont have lockdep support in all
> architectures - 3 years and counting. It's a highly useful purely
> sw feature with zero hardware dependencies. Fortunately it's
> well-modularized and the functionality is non-essential. Percpu
> allocation is not so lucky as it's essential functionality. )
When it coems to code coverage, x86 matters _so_ much more than any other
architecture, that verification features like lockdep etc are way more
important on x86 than on anything else.
Sure, there may be locking issues in some arch-specific code, and other
architectures could be better off caring. But the advantage of lockdep for
some pissant architecture that has a very limited user base (maybe lots of
chips, but much more limited _use_ - fewer drivers, fewer workloads etc)
is much lower, since those architectures know that x86 will give them 99%
of the coverage.
So it's quite reasonable to think that other architectures simply care
less.
Linus
next prev parent reply other threads:[~2009-06-19 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 8:07 Tejun Heo
2009-06-18 21:22 ` Linus Torvalds
2009-06-18 21:39 ` Andrew Morton
2009-06-18 22:43 ` Tejun Heo
2009-06-19 6:49 ` Ingo Molnar
2009-06-18 22:33 ` Tejun Heo
2009-06-18 22:45 ` Tejun Heo
2009-06-19 1:47 ` Tejun Heo
2009-06-19 5:39 ` Ingo Molnar
2009-06-19 19:39 ` Linus Torvalds [this message]
2009-06-19 21:08 ` Ingo Molnar
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=alpine.LFD.2.01.0906191235490.16802@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®