[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <F7783CD9-E807-4041-AD67-195E62A4D5CC@gmail.com>
Date: Wed, 8 Jul 2015 17:47:00 +0300
From: Dmitry Kalinkin <dmitry.kalinkin@...il.com>
To: Martyn Welch <martyn.welch@...com>
Cc: Alessio Igor Bogani <alessioigorbogani@...il.com>,
devel@...verdev.osuosl.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Igor Alekseev <igor.alekseev@...p.ru>,
LKML <linux-kernel@...r.kernel.org>,
Manohar Vanga <manohar.vanga@...il.com>
Subject: Re: [PATCHv3 08/16] staging: vme_user: provide DMA functionality
> On 08 Jul 2015, at 16:57, Martyn Welch <martyn.welch@...com> wrote:
>
>
>
> On 07/07/15 11:52, Dmitry Kalinkin wrote:
>> The API I had in mind would have only vme_master_read and
>> vme_master_write that would take absolute addresses (not relative to
>> any window). These variants of access functions would then try to
>> reuse any window that is already able to serve the request or wait
>> for a free window and reconfigure it for the need of the request.
>
> I'm a little concerned by the latency this might cause, especially if there is one device which is negatively affected by latency. Handling RORA interrupts would be "interesting" if all the windows were dynamically allocated at the time at which an interrupt came in.
Latency-critical windows can be statically allocated using current resource based API.--
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/
Powered by blists - more mailing lists