linux-kernel - Re: [PATCHv5] staging: vme_user: provide DMA functionality

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]

Date:	Mon, 19 Oct 2015 10:26:46 +0200
From:	Alessio Igor Bogani <alessioigorbogani@...il.com>
To:	Martyn Welch <martyn@...chs.me.uk>
Cc:	Dmitry Kalinkin <dmitry.kalinkin@...il.com>,
	devel@...verdev.osuosl.org,
	Manohar Vanga <manohar.vanga@...il.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Igor Alekseev <igor.alekseev@...p.ru>,
	LKML <linux-kernel@...r.kernel.org>, kbuild-all@...org
Subject: Re: [PATCHv5] staging: vme_user: provide DMA functionality

Hi,

On 19 October 2015 at 00:04, Martyn Welch <martyn@...chs.me.uk> wrote:
> On 18/10/15 18:53, Dmitry Kalinkin wrote:
[...]
>> Other drives meaning vme_pio, I don't see any others. All this time
>> we are discussing how many GE PIO boards one can plug into a crate
>> with or without vme_user. Most of people have zero of them.
>> Also, VME DMA API has no users in kernel, we are just adding one now.
>
>
> Unfortunately not all users of Linux upstream or even publicise their
> drivers. This is especially true of some industries where VME gets used. The
> number of VME windows is limited, so having a user space shim either hog or
> limit the number of resources available either in kernel space or user space
> is not an optimal solution.

We aren't an industry but we are exactly in that position: we have a
bunch of unpublished kernel driver for VME boards almost all built on
top of the customized old vmelinux.org stack.
We already tried to port a driver to current stack but we stuck on the
static resource management approach in particular for limited VME
windows (when the customization of the old stack was made for handle
VME windows dynamically).

Ciao,
Alessio
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/