Commit 166cfda7 authored by Seth Jennings's avatar Seth Jennings Committed by Greg Kroah-Hartman

staging: zsmalloc: add details to zs_map_object boiler plate

Add information on the usage limits of zs_map_object()
Signed-off-by: default avatarSeth Jennings <sjenning@linux.vnet.ibm.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent 10312330
...@@ -747,7 +747,12 @@ EXPORT_SYMBOL_GPL(zs_free); ...@@ -747,7 +747,12 @@ EXPORT_SYMBOL_GPL(zs_free);
* *
* Before using an object allocated from zs_malloc, it must be mapped using * Before using an object allocated from zs_malloc, it must be mapped using
* this function. When done with the object, it must be unmapped using * this function. When done with the object, it must be unmapped using
* zs_unmap_object * zs_unmap_object.
*
* Only one object can be mapped per cpu at a time. There is no protection
* against nested mappings.
*
* This function returns with preemption and page faults disabled.
*/ */
void *zs_map_object(struct zs_pool *pool, unsigned long handle) void *zs_map_object(struct zs_pool *pool, unsigned long handle)
{ {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment