lkml.org 
[lkml]   [2018]   [Feb]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 6/6] Documentation for Pmalloc
From
Date
On 04/02/18 23:37, Randy Dunlap wrote:

[...]

>> +reason, could neither be declared as constant, nor it could take advantage
>
> nor could it

ok

[...]

>> +Ex: A policy that is loaded from userspace.
>
> Either
> Example:
> or
> E.g.:
> (meaning For example)

ok

[...]

>> +Different kernel idrivers and threads can use different pools, for finer
>
> drivers

:-( ok

[...]

>> + in use anymore by the requestor, however it will not become avaiable for
>
> requester; however, available

ok

[...]

>> +- pmalloc does not provide locking support wrt allocating vs protecting
>
> Write out "wrt" -> with respect to.

ok

>> + an individual pool, for performance reason. It is recommended to not
>
> reasons. not to

ok & ok

[...]

>> + in the case of using directly vmalloc. The exact number depends on size
>
> of using vmalloc directly. on the size

ok & ok

[...]

>> +6. write protect the pool
>
> write-protect

ok

[...]

>> +7. use in read-only mode the handlers obtained through the allocations
>
> handles ??

yes

---
thanks, igor

\
 
 \ /
  Last update: 2018-02-09 17:42    [W:0.060 / U:4.508 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site