Minus the comment-fixes Mike Rapoport mentioned, looks good:
Reviewed-by: Jay Freyensee
On 2/28/18 12:06 PM, Igor Stoppa wrote:
Detailed documentation about the protectable memory allocator.
Signed-off-by: Igor Stoppa
---
Minus the comment-fixes Mike Rapoport mentioned, looks good:
Reviewed-by: Jay Freyensee
On 2/28/18 12:06 PM, Igor Stoppa wrote:
Detailed documentation about the protectable memory allocator.
Signed-off-by: Igor Stoppa
---
Documentation/core-api/index.rst | 1 +
On Wed, Feb 28, 2018 at 10:06:20PM +0200, Igor Stoppa wrote:
> Detailed documentation about the protectable memory allocator.
>
> Signed-off-by: Igor Stoppa
> ---
> Documentation/core-api/index.rst | 1 +
> Documentation/core-api/pmalloc.rst | 111
>
On Wed, Feb 28, 2018 at 10:06:20PM +0200, Igor Stoppa wrote:
> Detailed documentation about the protectable memory allocator.
>
> Signed-off-by: Igor Stoppa
> ---
> Documentation/core-api/index.rst | 1 +
> Documentation/core-api/pmalloc.rst | 111
> +
>
Detailed documentation about the protectable memory allocator.
Signed-off-by: Igor Stoppa
---
Documentation/core-api/index.rst | 1 +
Documentation/core-api/pmalloc.rst | 111 +
2 files changed, 112 insertions(+)
create mode
Detailed documentation about the protectable memory allocator.
Signed-off-by: Igor Stoppa
---
Documentation/core-api/index.rst | 1 +
Documentation/core-api/pmalloc.rst | 111 +
2 files changed, 112 insertions(+)
create mode 100644
[...]
On 2/26/18 7:39 AM, Igor Stoppa wrote:
On 24/02/18 02:26, J Freyensee wrote:
On 2/23/18 6:48 AM, Igor Stoppa wrote:
[...]
+- Before destroying a pool, all the memory allocated from it must be
+ released.
Is that true? pmalloc_destroy_pool() has:
.
.
+
[...]
On 2/26/18 7:39 AM, Igor Stoppa wrote:
On 24/02/18 02:26, J Freyensee wrote:
On 2/23/18 6:48 AM, Igor Stoppa wrote:
[...]
+- Before destroying a pool, all the memory allocated from it must be
+ released.
Is that true? pmalloc_destroy_pool() has:
.
.
+
On 24/02/18 02:26, J Freyensee wrote:
>
>
> On 2/23/18 6:48 AM, Igor Stoppa wrote:
[...]
>> +- Before destroying a pool, all the memory allocated from it must be
>> + released.
>
> Is that true? pmalloc_destroy_pool() has:
>
> .
> .
> + pmalloc_pool_set_protection(pool, false);
> +
On 24/02/18 02:26, J Freyensee wrote:
>
>
> On 2/23/18 6:48 AM, Igor Stoppa wrote:
[...]
>> +- Before destroying a pool, all the memory allocated from it must be
>> + released.
>
> Is that true? pmalloc_destroy_pool() has:
>
> .
> .
> + pmalloc_pool_set_protection(pool, false);
> +
On 2/23/18 6:48 AM, Igor Stoppa wrote:
Detailed documentation about the protectable memory allocator.
Signed-off-by: Igor Stoppa
---
Documentation/core-api/index.rst | 1 +
Documentation/core-api/pmalloc.rst | 114 +
2 files
On 2/23/18 6:48 AM, Igor Stoppa wrote:
Detailed documentation about the protectable memory allocator.
Signed-off-by: Igor Stoppa
---
Documentation/core-api/index.rst | 1 +
Documentation/core-api/pmalloc.rst | 114 +
2 files changed, 115
Detailed documentation about the protectable memory allocator.
Signed-off-by: Igor Stoppa
---
Documentation/core-api/index.rst | 1 +
Documentation/core-api/pmalloc.rst | 114 +
2 files changed, 115 insertions(+)
create mode
Detailed documentation about the protectable memory allocator.
Signed-off-by: Igor Stoppa
---
Documentation/core-api/index.rst | 1 +
Documentation/core-api/pmalloc.rst | 114 +
2 files changed, 115 insertions(+)
create mode 100644
14 matches
Mail list logo