From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Shaohua Li <shli-b10kYP2dOMg@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Adam Morrison
<mad-FrESSTt7Abv7r6psnUbsSmZHpeb/A1Y/@public.gmane.org>,
Kernel-team-b10kYP2dOMg@public.gmane.org
Subject: Re: [PATCH V2 0/4]IOMMU: avoid lock contention in iova allocation
Date: Wed, 20 Jan 2016 13:21:03 +0100 [thread overview]
Message-ID: <20160120122103.GE18805@8bytes.org> (raw)
In-Reply-To: <20160111033749.GA1811285-tb7CFzD8y5b7E6g3fPdp/g2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
On Sun, Jan 10, 2016 at 07:37:59PM -0800, Shaohua Li wrote:
> I don't know you already posted one. Roughly looked at the patches. We
> are using exactly the same idea. I'm happy we pursue your patches. At
> the first look, the per-cpu allocation in your patch doesn't check
> pfn_limit, that could be wrong, but should be easy to fix. I'll take a
> close look tomorrow.
Sounds great. Your approaches with the per-cpu are pretty similar, so I
would appreciate if you two come up with a combined patch-set?
Joerg
next prev parent reply other threads:[~2016-01-20 12:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 0:44 [PATCH V2 0/4]IOMMU: avoid lock contention in iova allocation Shaohua Li
[not found] ` <cover.1452297604.git.shli-b10kYP2dOMg@public.gmane.org>
2016-01-09 0:44 ` [PATCH V2 1/4] IOMMU: add a percpu cache for " Shaohua Li
2016-01-09 0:44 ` [PATCH V2 2/4] iommu: free_iova doesn't need lock twice Shaohua Li
2016-01-09 0:44 ` [PATCH V2 3/4] intel-iommu: remove find_iova in unmap path Shaohua Li
2016-01-09 0:44 ` [PATCH V2 4/4] intel-iommu: do batch iova free Shaohua Li
2016-01-10 22:56 ` [PATCH V2 0/4]IOMMU: avoid lock contention in iova allocation Adam Morrison
[not found] ` <20160110225610.GA16778-FrESSTt7Abv7r6psnUbsSmZHpeb/A1Y/@public.gmane.org>
2016-01-11 3:37 ` Shaohua Li
[not found] ` <20160111033749.GA1811285-tb7CFzD8y5b7E6g3fPdp/g2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2016-01-20 12:21 ` Joerg Roedel [this message]
[not found] ` <20160120122103.GE18805-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-01-20 18:10 ` Shaohua Li
[not found] ` <20160120180956.GA230160-tb7CFzD8y5b7E6g3fPdp/g2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2016-01-20 20:47 ` Adam Morrison
[not found] ` <CAHMfzJmAUWT8X4492_84smUgQMW9pW1yNfOxC6e7ur9TitA2cA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-20 21:14 ` Shaohua Li
[not found] ` <20160120211421.GA684235-tb7CFzD8y5b7E6g3fPdp/g2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2016-01-21 23:14 ` Adam Morrison
[not found] ` <20160121231326.GA16905-FrESSTt7Abv7r6psnUbsSmZHpeb/A1Y/@public.gmane.org>
2016-01-22 0:18 ` Shaohua Li
[not found] ` <20160122001801.GA4114061-tb7CFzD8y5b7E6g3fPdp/g2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2016-01-22 11:35 ` Adam Morrison
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160120122103.GE18805@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=Kernel-team-b10kYP2dOMg@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=mad-FrESSTt7Abv7r6psnUbsSmZHpeb/A1Y/@public.gmane.org \
--cc=shli-b10kYP2dOMg@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.