linux-kernel - Re: [RFC][PATCH 4/4] Rename lock_cpu_hotplug/unlock_cpu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 29 Aug 2006 13:03:04 -0700
From:	"Paul E. McKenney" <paulmck@...ibm.com>
To:	Paul Jackson <pj@....com>
Cc:	ego@...ibm.com, mingo@...e.hu, nickpiggin@...oo.com.au,
	arjan@...radead.org, rusty@...tcorp.com.au, torvalds@...l.org,
	akpm@...l.org, linux-kernel@...r.kernel.org, arjan@...el.linux.com,
	davej@...hat.com, dipankar@...ibm.com, vatsa@...ibm.com,
	ashok.raj@...el.com
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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/