linux-kernel - Re: [RFC 3/4] Documentation: move dma-buf documentation to rst

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <7000584B-8BE3-4948-8DB2-4088F3C88295@darmarit.de>
Date:	Thu, 11 Aug 2016 14:12:03 +0200
From:	Markus Heiser <markus.heiser@...marit.de>
To:	Sumit Semwal <sumit.semwal@...aro.org>
Cc:	"linux-media@...r.kernel.org Mailing List" 
	<linux-media@...r.kernel.org>,
	"dri-devel@...ts.freedesktop.org Development" 
	<dri-devel@...ts.freedesktop.org>, linaro-mm-sig@...ts.linaro.org,
	linux-doc@...r.kernel.org,
	"corbet@....net Corbet" <corbet@....net>,
	"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC 3/4] Documentation: move dma-buf documentation to rst


Am 11.08.2016 um 13:58 schrieb Markus Heiser <markus.heiser@...marit.de>:
>> +.. note:: Until this stage, the buffer-exporter has the option to choose not to
>> +   actually allocate the backing storage for this buffer, but wait for the
>> +   first buffer-user to request use of buffer for allocation.
> 
> Use newlines ... which are markups in reST ;)
> 
> .. note:: 
> 
> Until this stage, the buffer-exporter has the option to choose not to
> actually allocate the backing storage for this buffer, but wait for the
> first buffer-user to request use of buffer for allocation.
> 

Sorry, my f... apple mail drops leading whitespaces ...

|.. note::
|
|   Until this stage, the buffer-exporter has the option to choose not to
|   actually allocate the backing storage for this buffer, but wait for the

>> +Kernel cpu access to a dma-buf buffer object
>> +============================================
>> +
>> +The motivation to allow cpu access from the kernel to a dma-buf object from the
>> +importers side are:
>> +
>> +* fallback operations, e.g. if the devices is connected to a usb bus and the
>> +  kernel needs to shuffle the data around first before sending it away.
>> +* full transparency for existing users on the importer side, i.e. userspace
>> +  should not notice the difference between a normal object from that subsystem
>> +  and an imported one backed by a dma-buf. This is really important for drm
>> +  opengl drivers that expect to still use all the existing upload/download
>> +  paths.
> 
> I is recommended to separate blocks (in this case the list item blocks) with
> a newline. E.g.
> 
> * first lorem
> ipsum
> 
> * second lorem
> ipsum
> 
> If you have only one-liners, it is OK to write
> 
> * first
> * second
> 

same here, leading whitespace are droped by the mail client.

|* first lorem
|  ipsum
|
|* second lorem
|  ipsum

Sorry for disorientation. For a snatch I forgot, that 
that Apple & MS have a mistaken idea of "plain text" ;)


-- Markus --