On 08/03/2016 06:34 PM, Benjamin Herrenschmidt wrote:
I think this is best done by the relevant community maintainer,
I just threw an idea but I'm not that familiar with the details:-)
Ok, sure; got it.
Did you send them to the lkml list ?
Yup, plus a few others lists from get_maintainer.pl
On Wed, 2016-08-03 at 16:39 -0300, Mauricio Faria de Oliveira wrote:
> Hi Ben,
>
> On 06/13/2016 06:26 PM, Benjamin Herrenschmidt wrote:
> >
> > Another option would be to use a dma_attr for silencing mapping
> > errors
> > which NVME could use provided it does handle them gracefully ...
>
> I r
Hi Ben,
On 06/13/2016 06:26 PM, Benjamin Herrenschmidt wrote:
Another option would be to use a dma_attr for silencing mapping errors
which NVME could use provided it does handle them gracefully ...
I recently submitted patches that implement your suggestion [1].
May you please review/comment i
On 06/13/2016 06:51 PM, Benjamin Herrenschmidt wrote:
Approximate wasn't a great choice of word but what I meant is:
- The size doesn't mean you can do an allocation that size (pools
layout etc..)
- And it might be shared with another device (though less likely
these days).
Ah, yup - ok
On Mon, 2016-06-13 at 18:43 -0300, Mauricio Faria de Oliveira wrote:
> Hi Ben,
>
> On 06/13/2016 06:26 PM, Benjamin Herrenschmidt wrote:
> > I've been thinking about this a bit... it might be worthwhile adding
> > a dma_* call to query the approximate size of the IOMMU window, as
> > a way for the
Hi Ben,
On 06/13/2016 06:26 PM, Benjamin Herrenschmidt wrote:
I've been thinking about this a bit... it might be worthwhile adding
a dma_* call to query the approximate size of the IOMMU window, as
a way for the device to adjust its requirements dynamically.
Ok, cool; something like it was one
On Mon, 2016-06-13 at 10:27 -0300, Mauricio Faria de Oliveira wrote:
> Hi Ben,
>
> On 06/11/2016 08:02 PM, Benjamin Herrenschmidt wrote:
> > I'm not fan of this. This is a very useful message to diagnose why,
> > for example, your network adapter is not working properly.
> >
> > A lot of drivers
Hi Ben,
On 06/11/2016 08:02 PM, Benjamin Herrenschmidt wrote:
I'm not fan of this. This is a very useful message to diagnose why,
for example, your network adapter is not working properly.
A lot of drivers don't deal well with IOMMU errors.
The fact that NVME trigger these is a problem that ne
On Fri, 2016-06-10 at 10:03 -0300, Mauricio Faria de Oliveira wrote:
> This prevents flooding the logs with 'iommu_alloc failed' messages
> while I/O is performed (normally) to very fast devices (e.g. NVMe).
>
> That error is not necessarily a problem; device drivers can retry
> later / reschedule
This prevents flooding the logs with 'iommu_alloc failed' messages
while I/O is performed (normally) to very fast devices (e.g. NVMe).
That error is not necessarily a problem; device drivers can retry
later / reschedule the requests for which the allocation failed,
and handle things gracefully for
10 matches
Mail list logo
