From: Manfred Spraul <manfred@colorfullife.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org, Keith Owens <kaos@ocs.com.au>
Subject: Re: [RFC] Lock free fd lookup
Date: Sat, 17 Jul 2004 10:50:48 +0200 [thread overview]
Message-ID: <40F8E868.7000008@colorfullife.com> (raw)
wli wrote
>> * It requires type stable storage. That is, once a data area has been
>> allocated to a particular structure type, it always contains that
>> structure type, even when it has been freed from the list. Each list
>> requires its own free pool, which can never be returned to the OS.
>
>The last of these is particularly lethal.
>
>
It might be possible to combine such a lock free algorithms with RCU and
then set Hugh's SLAB_DESTROY_BY_RCU: It inserts a call_rcu between
leaving the free pool and returning the page to the OS.
--
Manfred
next reply other threads:[~2004-07-17 8:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-17 8:50 Manfred Spraul [this message]
2004-07-17 9:30 ` [RFC] Lock free fd lookup William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2004-07-17 19:17 Albert Cahalan
2004-07-29 0:14 ` William Lee Irwin III
2004-07-14 4:53 [RFC] Refcounting of objects part of a lockfree collection Ravikiran G Thirumalai
2004-07-14 4:56 ` [RFC] Lock free fd lookup Ravikiran G Thirumalai
2004-07-14 15:17 ` Chris Wright
2004-07-15 14:22 ` Jesse Barnes
2004-07-15 16:10 ` Dipankar Sarma
2004-07-15 16:22 ` Jesse Barnes
2004-07-15 16:34 ` Chris Wright
2004-07-16 5:38 ` Ravikiran G Thirumalai
2004-07-16 6:27 ` William Lee Irwin III
2004-07-17 0:55 ` Keith Owens
2004-07-17 1:19 ` William Lee Irwin III
2004-07-17 2:12 ` Keith Owens
2004-07-17 2:34 ` William Lee Irwin III
2004-07-17 2:28 ` Keith Owens
2004-07-17 3:16 ` William Lee Irwin III
2004-07-17 13:48 ` Peter Zijlstra
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=40F8E868.7000008@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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.