mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: paulmck@linux.vnet.ibm.com
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [RFC, PATCH] kernel/rcu: add kfree_rcu
Date: Mon, 05 Jan 2009 08:15:45 +0100	[thread overview]
Message-ID: <4961B3A1.3070009@colorfullife.com> (raw)
In-Reply-To: <20090104194851.GM6958@linux.vnet.ibm.com>

Paul E. McKenney wrote:
>
>> I think these two are different questions.
>> vfree() still can not be called from softirq context now.
>> And I proposed vfree_atomic() for RCU, but it can not be accepted.
>>     
>
> And one would indeed either need to have a vfree_atomic() or have some
> mechanism that sent the vfree() to a workqueue or some such.
>   
ipc/util.c uses a workqueue (ipc_schedule_free):
The semaphore array structure can be large (documented with SEMMSL=8000 
around 16 kB, but there is no  hard limit), thus vmalloc is used.

But as long as there are just one or two users, I doubt that a generic 
system is worth the effort.

--
    Manfred


  parent reply	other threads:[~2009-01-05  7:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02 11:25 Manfred Spraul
2009-01-02 18:55 ` Paul E. McKenney
2009-01-03 14:59   ` Manfred Spraul
2009-01-03 23:46     ` Paul E. McKenney
2009-01-04  5:50   ` Lai Jiangshan
2009-01-04 19:48     ` Paul E. McKenney
2009-01-05  2:48       ` Lai Jiangshan
2009-01-05  4:40         ` Paul E. McKenney
2009-01-06 22:17           ` Paul E. McKenney
2009-01-05  7:15       ` Manfred Spraul [this message]
2009-01-04  5:39 ` Lai Jiangshan
2009-01-04  7:07   ` Manfred Spraul
2009-01-04  8:30     ` Lai Jiangshan
2009-01-04 12:22       ` Manfred Spraul
2009-01-04 20:06         ` Paul E. McKenney
2009-01-12 17:43           ` Paul E. McKenney

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=4961B3A1.3070009@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=akpm@linux-foundation.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome