All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Mao <maoming.maoming@huawei.com>
To: <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>,
	<linux-mm@kvack.org>, <alex.williamson@redhat.com>,
	<akpm@linux-foundation.org>
Cc: <cohuck@redhat.com>, <jianjay.zhou@huawei.com>,
	<weidong.huang@huawei.com>, <peterx@redhat.com>,
	<aarcange@redhat.com>, <wangyunjian@huawei.com>,
	Ming Mao <maoming.maoming@huawei.com>
Subject: [PATCH V4 0/2] vfio: optimized for hugetlbf pages when dma map/unmap
Date: Tue, 8 Sep 2020 21:32:02 +0800	[thread overview]
Message-ID: <20200908133204.1338-1-maoming.maoming@huawei.com> (raw)

This series deletes the for loop in dma_map/unmap for hugetlb pages.
In the original process, the for loop could spend much time to check all
normal pages.If we use hugetlb pages, it is not necessary to do this.

Changes from v3
- add a new API unpin_user_hugetlb_pages_dirty_lock()
- use the new API to unpin hugetlb pages

Ming Mao (2):
  vfio dma_map/unmap: optimized for hugetlbfs pages
  vfio: optimized for unpinning pages

 drivers/vfio/vfio_iommu_type1.c | 373 ++++++++++++++++++++++++++++++--
 include/linux/mm.h              |   3 +
 mm/gup.c                        |  91 ++++++++
 3 files changed, 450 insertions(+), 17 deletions(-)

-- 
2.23.0



             reply	other threads:[~2020-09-08 15:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08 13:32 Ming Mao [this message]
2020-09-08 13:32 ` [PATCH V4 1/2] vfio dma_map/unmap: optimized for hugetlbfs pages Ming Mao
2020-09-09  8:01   ` Christoph Hellwig
2020-09-09 13:05     ` Jason Gunthorpe
2020-09-09 14:29       ` Christoph Hellwig
2020-09-09 15:00         ` Matthew Wilcox
2020-09-09 15:09         ` Jason Gunthorpe
2020-09-09 13:41     ` Matthew Wilcox
2020-09-09 17:04     ` Matthew Wilcox
2020-09-08 13:32 ` [PATCH V4 2/2] vfio: optimized for unpinning pages Ming Mao

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=20200908133204.1338-1-maoming.maoming@huawei.com \
    --to=maoming.maoming@huawei.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.williamson@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=peterx@redhat.com \
    --cc=wangyunjian@huawei.com \
    --cc=weidong.huang@huawei.com \
    /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.