From 939273f1e8844e9abf5652ec7166014a0ab4f674 Mon Sep 17 00:00:00 2001 From: "Reynaldo H. Verdejo Pinochet" Date: Fri, 13 Jan 2017 14:13:23 -0800 Subject: [PATCH] design: buffer: add missing markup and ()s to func references Additionally, rework paragraph to avoid redundancy. --- markdown/design/buffer.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/markdown/design/buffer.md b/markdown/design/buffer.md index 9151c5bb6c..dea8e4a55a 100644 --- a/markdown/design/buffer.md +++ b/markdown/design/buffer.md @@ -68,13 +68,13 @@ Accessing the data of the buffer can happen by retrieving the individual `GstMemory` objects in the `GstBuffer` or by using the `gst_buffer_map()` and `gst_buffer_unmap()` functions. -The `_map` and `_unmap` functions will always return the memory of all blocks as -one large contiguous region of memory. Using the `_map` and `_unmap` functions -might be more convenient than accessing the individual memory blocks at the -expense of being more expensive because it might perform memcpy operations. +The `_map()` and `_unmap()` functions will always return the memory of all +blocks as one large contiguous region. Using these functions might be more +convenient than accessing the individual memory blocks at the expense of +being more expensive because it might perform memcpy operations. -For buffers with only one `GstMemory` object (the most common case), `_map` and -`_unmap` have no performance penalty at all. +For buffers with only one `GstMemory` object (the most common case), `_map()` +and `_unmap()` have no performance penalty at all. - **Read access with 1 memory block**: The memory block is accessed and mapped for read access. The memory block is unmapped after usage