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: <Pine.LNX.4.44L0.1807171643120.1344-100000@iolanthe.rowland.org>
Date:   Tue, 17 Jul 2018 16:51:10 -0400 (EDT)
From:   Alan Stern <stern@...land.harvard.edu>
To:     Ezequiel Garcia <ezequiel@...labora.com>
cc:     "Matwey V. Kornilov" <matwey@....msu.ru>,
        Hans de Goede <hdegoede@...hat.com>, <hverkuil@...all.nl>,
        <mchehab@...nel.org>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        <rostedt@...dmis.org>, <mingo@...hat.com>, <isely@...ox.com>,
        <bhumirks@...il.com>, <colin.king@...onical.com>,
        <linux-media@...r.kernel.org>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] media: usb: pwc: Don't use coherent DMA buffers for
 ISO transfer

On Tue, 17 Jul 2018, Ezequiel Garcia wrote:

> Hi Matwey,
> 
> First of all, sorry for the delay.
> 
> Adding Alan and Hans. Guys, do you have any feedback here?

...

> > > So, what is the benefit of using consistent
> > > for these URBs, as opposed to streaming?
> > 
> > I don't know, I think there is no real benefit and all we see is a
> > consequence of copy-pasta when some webcam drivers were inspired by
> > others and development priparily was going at x86 platforms.
> 
> You are probably right about the copy-pasta.
> 
> >  It would
> > be great if somebody corrected me here. DMA Coherence is quite strong
> > property and I cannot figure out how can it help when streaming video.
> > The CPU host always reads from the buffer and never writes to.
> > Hardware perepherial always writes to and never reads from. Moreover,
> > buffer access is mutually exclusive and separated in time by Interrupt
> > fireing and URB starting (when we reuse existing URB for new request).
> > Only single one memory barrier is really required here.
> > 
> 
> Yeah, and not setting URB_NO_TRANSFER_DMA_MAP makes the USB core
> create DMA mappings and use the streaming API. Which makes more
> sense in hardware without hardware coherency.

As far as I know, the _only_ advantage to using coherent DMA in this
situation is that you then do not have to pay the overhead of
constantly setting up and tearing down the streaming mappings.  So it
depends very much on the platform: If coherent buffers are cached then
it's a slight win and otherwise it's a big lose.

Alan Stern

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ