From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Song Bao Hua (Barry Song)" <song.bao.hua@hisilicon.com>
Cc: "Wangzhou (B)" <wangzhou1@hisilicon.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
"linux-accelerators@lists.ozlabs.org"
<linux-accelerators@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Liguozhu (Kenneth)" <liguozhu@hisilicon.com>,
"chensihang (A)" <chensihang1@hisilicon.com>
Subject: Re: [RFC PATCH v2] uacce: Add uacce_ctrl misc device
Date: Mon, 25 Jan 2021 19:16:19 -0400 [thread overview]
Message-ID: <20210125231619.GY4605@ziepe.ca> (raw)
In-Reply-To: <96b655ade2534a65974a378bb68383ee@hisilicon.com>
On Mon, Jan 25, 2021 at 10:21:14PM +0000, Song Bao Hua (Barry Song) wrote:
> mlock, while certainly be able to prevent swapping out, it won't
> be able to stop page moving due to:
> * memory compaction in alloc_pages()
> * making huge pages
> * numa balance
> * memory compaction in CMA
Enabling those things is a major reason to have SVA device in the
first place, providing a SW API to turn it all off seems like the
wrong direction.
If the device doesn't want to use SVA then don't use it, use normal
DMA pinning like everything else.
Jason
next prev parent reply other threads:[~2021-01-25 23:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 8:34 [RFC PATCH v2] uacce: Add uacce_ctrl misc device Zhou Wang
2021-01-25 9:28 ` Greg Kroah-Hartman
2021-01-25 12:47 ` Zhou Wang
2021-01-25 15:47 ` Jason Gunthorpe
2021-01-25 22:21 ` Song Bao Hua (Barry Song)
2021-01-25 23:16 ` Jason Gunthorpe [this message]
2021-01-25 23:35 ` Song Bao Hua (Barry Song)
2021-01-26 1:13 ` Jason Gunthorpe
2021-01-26 1:26 ` Song Bao Hua (Barry Song)
2021-01-26 18:20 ` Jason Gunthorpe
2021-01-28 1:28 ` Song Bao Hua (Barry Song)
[not found] ` <MWHPR11MB1886DC78C5FBA3636B94F2578CB99@MWHPR11MB1886.namprd11.prod.outlook.com>
2021-02-01 23:44 ` Jason Gunthorpe
2021-02-02 0:22 ` Song Bao Hua (Barry Song)
2021-02-02 2:51 ` Tian, Kevin
2021-02-02 3:47 ` Song Bao Hua (Barry Song)
2021-01-26 9:00 ` Zhou Wang
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=20210125231619.GY4605@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=arnd@arndb.de \
--cc=chensihang1@hisilicon.com \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=liguozhu@hisilicon.com \
--cc=linux-accelerators@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=song.bao.hua@hisilicon.com \
--cc=wangzhou1@hisilicon.com \
--cc=zhangfei.gao@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).