From: Peter Zijlstra <peterz@infradead.org>
To: Salman Qazi <sqazi@google.com>
Cc: paulmck@us.ibm.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, adurbin@google.com,
Nick Piggin <npiggin@gmail.com>
Subject: Re: [PATCH] Fixed a mismatch between the users of radix_tree and the implementation.
Date: Tue, 17 Aug 2010 10:42:51 +0200 [thread overview]
Message-ID: <1282034571.1926.2143.camel@laptop> (raw)
In-Reply-To: <AANLkTimk_16nz2BWB42yHAAseaEJP-DBdondBO5oznrQ@mail.gmail.com>
On Mon, 2010-08-16 at 21:45 -0700, Salman Qazi wrote:
> But considering that the kernel locks up, and we are still talking
> about < 5MB after a kernel compile, should we really be all that
> concerned? If so, what are the alternatives that should be considered
> for fixing this lock up?
No bright ideas atm, but yeah, that indirect pointer vs rcu slot lookup
is funky. Lets go with your patch for now.
Maybe Nick has a bright idea?
next prev parent reply other threads:[~2010-08-17 8:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 7:15 [PATCH] Fixed a mismatch between the users of radix_tree and the implementation Salman Qazi
2010-08-13 7:20 ` Salman Qazi
2010-08-16 11:25 ` Peter Zijlstra
2010-08-16 18:30 ` Salman Qazi
2010-08-16 19:33 ` Peter Zijlstra
[not found] ` <AANLkTindpUo5tPiXVp6wXjOAqczrJvYegrOMBqSjr4_t@mail.gmail.com>
2010-08-16 21:05 ` Salman Qazi
2010-08-16 21:06 ` Peter Zijlstra
2010-08-17 4:35 ` Salman Qazi
2010-08-17 4:45 ` Salman Qazi
2010-08-17 8:42 ` Peter Zijlstra [this message]
2010-08-17 15:23 ` Nick Piggin
2010-08-17 15:48 ` Peter Zijlstra
2010-08-17 19:49 ` Salman Qazi
2010-08-17 21:28 ` Salman Qazi
2010-08-30 23:27 ` Salman Qazi
2010-11-10 19:16 ` Salman Qazi
2010-11-11 0:29 ` Nick Piggin
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=1282034571.1926.2143.camel@laptop \
--to=peterz@infradead.org \
--cc=adurbin@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=paulmck@us.ibm.com \
--cc=sqazi@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.