> On 08 Jul 2015, at 16:57, Martyn Welch <martyn.we...@ge.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 majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
