Messages in this thread | | | Date | Tue, 29 Aug 2006 13:03:04 -0700 | From | "Paul E. McKenney" <> | Subject | Re: [RFC][PATCH 4/4] Rename lock_cpu_hotplug/unlock_cpu_hotplug |
| |
On Tue, Aug 29, 2006 at 12:31:02PM -0700, Paul Jackson wrote: > Paul E. McKenney wrtoe: > > Can the locusts reasonably take a return value from the acquisition > > primitive and feed it to the release primitive? > > Yes - the locusts typically do: > > mutex_lock(&callback_mutex); > ... a line or two to read or write cpusets ... > mutex_unlock(&callback_mutex); > > The lock and unlock are just a few lines apart. I could easily pass > a value from the lock (acquisition) to the unlock (release). > > Why do you ask?
Because passing the value from the acquire to the release could remove the need to store anything in the task structure, but allow the freedom of implementation that would be provided by storing things in the task structure.
Let me throw something together...
Thanx, 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/
| |