Re: [PATCH] iommu/iova: Update cached node pointer when current node fails to get any free IOVA

Hi Robin, On Mon, Jul 30, 2018 at 12:40 PM, Ganapatrao Kulkarni wrote: > On Fri, Jul 27, 2018 at 9:48 PM, Robin Murphy wrote: >> On 27/07/18 13:56, Ganapatrao Kulkarni wrote: >> [...] > > did you get any chance to look in to this issue? > i am waiting for your suggestion/patch for

Re: [PATCH] iommu/iova: Update cached node pointer when current node fails to get any free IOVA

On Fri, Jul 27, 2018 at 9:48 PM, Robin Murphy wrote: > On 27/07/18 13:56, Ganapatrao Kulkarni wrote: > [...] did you get any chance to look in to this issue? i am waiting for your suggestion/patch for this issue! >>> >>> >>> >>> I got as far as [1], but I wasn't sure how much I

Re: [PATCH] iommu/iova: Update cached node pointer when current node fails to get any free IOVA

On 27/07/18 13:56, Ganapatrao Kulkarni wrote: [...] did you get any chance to look in to this issue? i am waiting for your suggestion/patch for this issue! I got as far as [1], but I wasn't sure how much I liked it, since it still seems a little invasive for such a specific case (plus I can't

Re: [PATCH] iommu/iova: Update cached node pointer when current node fails to get any free IOVA

Hi Robin, On Wed, Jul 25, 2018 at 7:50 PM, Robin Murphy wrote: > On 12/07/18 08:45, Ganapatrao Kulkarni wrote: >> >> Hi Robin, >> >> >> On Mon, Jun 4, 2018 at 9:36 AM, Ganapatrao Kulkarni >> wrote: >>> >>> ping?? >>> >>> On Mon, May 21, 2018 at 6:45 AM, Ganapatrao Kulkarni >>> wrote:

Re: [PATCH] iommu/iova: Update cached node pointer when current node fails to get any free IOVA

On 12/07/18 08:45, Ganapatrao Kulkarni wrote: Hi Robin, On Mon, Jun 4, 2018 at 9:36 AM, Ganapatrao Kulkarni wrote: ping?? On Mon, May 21, 2018 at 6:45 AM, Ganapatrao Kulkarni wrote: On Thu, Apr 26, 2018 at 3:15 PM, Ganapatrao Kulkarni wrote: Hi Robin, On Mon, Apr 23, 2018 at 11:11 PM,

Re: [PATCH] iommu/iova: Update cached node pointer when current node fails to get any free IOVA

Hi Robin, On Mon, Jun 4, 2018 at 9:36 AM, Ganapatrao Kulkarni wrote: > ping?? > > On Mon, May 21, 2018 at 6:45 AM, Ganapatrao Kulkarni > wrote: >> On Thu, Apr 26, 2018 at 3:15 PM, Ganapatrao Kulkarni >> wrote: >>> Hi Robin, >>> >>> On Mon, Apr 23, 2018 at 11:11 PM, Ganapatrao Kulkarni >>>

Re: [PATCH] iommu/iova: Update cached node pointer when current node fails to get any free IOVA

ping?? On Mon, May 21, 2018 at 6:45 AM, Ganapatrao Kulkarni wrote: > On Thu, Apr 26, 2018 at 3:15 PM, Ganapatrao Kulkarni > wrote: >> Hi Robin, >> >> On Mon, Apr 23, 2018 at 11:11 PM, Ganapatrao Kulkarni >> wrote: >>> On Mon, Apr 23, 2018 at 10:07 PM, Robin Murphy wrote: On 19/04/18

Re: [PATCH] iommu/iova: Update cached node pointer when current node fails to get any free IOVA

On Thu, Apr 26, 2018 at 3:15 PM, Ganapatrao Kulkarni wrote: > Hi Robin, > > On Mon, Apr 23, 2018 at 11:11 PM, Ganapatrao Kulkarni > wrote: >> On Mon, Apr 23, 2018 at 10:07 PM, Robin Murphy wrote: >>> On 19/04/18 18:12, Ganapatrao

Re: [PATCH] iommu/iova: Update cached node pointer when current node fails to get any free IOVA

Hi Robin, On Mon, Apr 23, 2018 at 11:11 PM, Ganapatrao Kulkarni wrote: > On Mon, Apr 23, 2018 at 10:07 PM, Robin Murphy wrote: >> On 19/04/18 18:12, Ganapatrao Kulkarni wrote: >>> >>> The performance drop is observed with long hours iperf testing using

Re: [PATCH] iommu/iova: Update cached node pointer when current node fails to get any free IOVA

On Mon, Apr 23, 2018 at 10:07 PM, Robin Murphy wrote: > On 19/04/18 18:12, Ganapatrao Kulkarni wrote: >> >> The performance drop is observed with long hours iperf testing using 40G >> cards. This is mainly due to long iterations in finding the free iova >> range in 32bit

Re: [PATCH] iommu/iova: Update cached node pointer when current node fails to get any free IOVA

On 19/04/18 18:12, Ganapatrao Kulkarni wrote: The performance drop is observed with long hours iperf testing using 40G cards. This is mainly due to long iterations in finding the free iova range in 32bit address space. In current implementation for 64bit PCI devices, there is always first

[PATCH] iommu/iova: Update cached node pointer when current node fails to get any free IOVA

The performance drop is observed with long hours iperf testing using 40G cards. This is mainly due to long iterations in finding the free iova range in 32bit address space. In current implementation for 64bit PCI devices, there is always first attempt to allocate iova from 32bit(SAC preferred