On Thu, 3 May 2007, Andrew Morton wrote: > Well that's the "locking" protocol then: each instance of this structure is > only ever touched by a single thread, yes? Yes. Each do_revoke() call creates a new instance. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH 2/2] revoke: change revoke_table to fileset and revoke_details
- From: Pekka J Enberg <[email protected]>
- Re: [PATCH 2/2] revoke: change revoke_table to fileset and revoke_details
- From: Andrew Morton <[email protected]>
- Re: [PATCH 2/2] revoke: change revoke_table to fileset and revoke_details
- From: Pekka J Enberg <[email protected]>
- Re: [PATCH 2/2] revoke: change revoke_table to fileset and revoke_details
- From: Andrew Morton <[email protected]>
- [PATCH 2/2] revoke: change revoke_table to fileset and revoke_details
- Prev by Date: Re: + per-cpuset-hugetlb-accounting-and-administration.patch added to -mm tree
- Next by Date: Re: + per-cpuset-hugetlb-accounting-and-administration.patch added to -mm tree
- Previous by thread: Re: [PATCH 2/2] revoke: change revoke_table to fileset and revoke_details
- Next by thread: Broken process startup times after suspend (regression)
- Index(es):
 |