On Thu, 04 Sep 2008 12:52:19 +1000 Benjamin Herrenschmidt [EMAIL PROTECTED]
wrote:
On Wed, 2008-09-03 at 15:41 +0200, Sebastien Dugue wrote:
On Wed, 20 Aug 2008 15:23:01 +1000 Benjamin Herrenschmidt [EMAIL
PROTECTED] wrote:
BTW. It would be good to try to turn the GFP_ATOMIC into
There's nothing to 'de-initialize' here, or am I missing something?
radix_tree_insert() will return ENOMEM and won't insert anything.
Forget my comment, just fallback.
Or you can fallback if you don't find, as easy, probably
easier since it shouldn't happen in practice.
That's what
On Thu, 04 Sep 2008 17:58:56 +1000 Benjamin Herrenschmidt [EMAIL PROTECTED]
wrote:
There's nothing to 'de-initialize' here, or am I missing something?
radix_tree_insert() will return ENOMEM and won't insert anything.
Forget my comment, just fallback.
Or you can fallback if you
The radix trees used by interrupt controllers for their irq reverse mapping
(currently only the XICS found on pSeries) have a complex locking scheme
dating back to before the advent of the lockless radix tree.
Take advantage of this and of the fact that the items of the tree are
pointers to a
On Wed, 20 Aug 2008 15:22:06 +1000 Benjamin Herrenschmidt [EMAIL PROTECTED]
wrote:
On Wed, 2008-08-06 at 15:30 +0200, Sebastien Dugue wrote:
The radix trees used by interrupt controllers for their irq reverse mapping
(currently only the XICS found on pSeries) have a complex locking scheme
On Wed, 20 Aug 2008 15:23:01 +1000 Benjamin Herrenschmidt [EMAIL PROTECTED]
wrote:
BTW. It would be good to try to turn the GFP_ATOMIC into GFP_KERNEL,
That would be nice indeed
maybe using a semaphore instead of a lock to protect insertion vs.
initialisation.
a semaphore? are you
On Wed, 2008-09-03 at 15:41 +0200, Sebastien Dugue wrote:
On Wed, 20 Aug 2008 15:23:01 +1000 Benjamin Herrenschmidt [EMAIL PROTECTED]
wrote:
BTW. It would be good to try to turn the GFP_ATOMIC into GFP_KERNEL,
That would be nice indeed
maybe using a semaphore instead of a lock to
On Wed, 2008-08-06 at 15:30 +0200, Sebastien Dugue wrote:
The radix trees used by interrupt controllers for their irq reverse mapping
(currently only the XICS found on pSeries) have a complex locking scheme
dating back to before the advent of the lockless radix tree.
Take advantage of this
BTW. It would be good to try to turn the GFP_ATOMIC into GFP_KERNEL,
maybe using a semaphore instead of a lock to protect insertion vs.
initialisation. The old scheme was fine because if the atomic allocation
failed, it could fallback to the linear search and try again on the next
interrupt. Not
The radix trees used by interrupt controllers for their irq reverse mapping
(currently only the XICS found on pSeries) have a complex locking scheme
dating back to before the advent of the lockless radix tree.
Take advantage of this and of the fact that the items of the tree are
pointers to a
10 matches
Mail list logo
