Messages in this thread | | | Date | Mon, 12 Feb 2007 01:52:00 -0800 | From | Paul Jackson <> | Subject | Re: [PATCH 0/7] containers (V7): Generic Process Containers |
| |
Paul M, responding to Paul J: > I think it could be made smarter than that, e.g. have a workqueue task > that's only woken when a refcount does actually reach zero. (I think > that waking a workqueue task is something that can be done without too > much worry about locks) > > > > > Can you explain to me how this intruded on the reference counting? > > > > Essentially, it means that anything that releases a reference count on > a container needs to be able to trigger a call to the release agent. > The reference count is often released at a point when important locks > are held, so you end up having to pass buffers into any function that > might drop a ref count, in order to store a path to a release agent to > be invoked.
Ok - now that you put it like that - it's much more persuasive.
Consider me sold on this aspect of your proposal, until and unless I protest otherwise, which is not likely.
Thanks.
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.925.600.0401 - 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/
| |