From bff7e4012b36ba580cd0198efe24d95f3c403e9f Mon Sep 17 00:00:00 2001 From: "Reynaldo H. Verdejo Pinochet" Date: Mon, 27 Feb 2017 15:15:57 -0800 Subject: [PATCH] design: memory: merge redundant offset/size explanation --- markdown/design/memory.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/markdown/design/memory.md b/markdown/design/memory.md index d4f663aaf7..3427a41099 100644 --- a/markdown/design/memory.md +++ b/markdown/design/memory.md @@ -12,13 +12,10 @@ multimedia data passed around in the pipeline. ## Memory layout -`GstMemory` manages a memory region. The accessible part of the managed region -is defined by an offset relative to the start of the region and a size. This -means that the managed region can be larger than what is visible to the user of -`GstMemory` API. - -Schematically, `GstMemory` has a pointer to a memory region of _maxsize_. The -area starting from `offset` and `size` is accessible. +A `GstMemory` has a pointer to a memory region of `maxsize`. The accessible part +of this managed region is defined by an `offset` relative to the start of the +region and a `size`. This means that the managed region can be larger than what +is visible to the user of the `GstMemory` API. ``` memory