On 7/17/07, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
Ok.. so my problem still remains, how do I get a non-blocking atomic reference increment/decrement routine, that would prevent my container from being deleted?
css_put() in my new patchset will be non-blocking.
I don't find cpusets using css_put().
Cpusets never needs to keep a non-process reference on a cpuset object, so the framework handles everything. Paul - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Containers: css_put() dilemma
- From: Balbir Singh <balbir@linux.vnet.ibm.com>
- Re: Containers: css_put() dilemma
- From: Balbir Singh <balbir@linux.vnet.ibm.com>
- Re: Containers: css_put() dilemma
- From: "Paul (宝瑠) Menage" <menage@google.com>
- Re: Containers: css_put() dilemma
- From: Balbir Singh <balbir@linux.vnet.ibm.com>
- Re: Containers: css_put() dilemma
- From: "Paul (宝瑠) Menage" <menage@google.com>
- Re: Containers: css_put() dilemma
- From: Balbir Singh <balbir@linux.vnet.ibm.com>
- Re: Containers: css_put() dilemma
- From: "Paul (宝瑠) Menage" <menage@google.com>
- Re: Containers: css_put() dilemma
- From: Balbir Singh <balbir@linux.vnet.ibm.com>
- Re: Containers: css_put() dilemma
- From: "Paul (宝瑠) Menage" <menage@google.com>
- Re: Containers: css_put() dilemma
- From: Balbir Singh <balbir@linux.vnet.ibm.com>
- Containers: css_put() dilemma
- Prev by Date: Re: [PATCH] posix-timer: fix deletion race
- Next by Date: Re: fbdev: make fb_append_extra_logo() depend on fb=y
- Previous by thread: Re: Containers: css_put() dilemma
- Next by thread: Re: Containers: css_put() dilemma
- Index(es):
 |