From: Moritz Fischer <mdf@kernel.org>
To: John Hubbard <jhubbard@nvidia.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Xu Yilun <yilun.xu@intel.com>, Wu Hao <hao.wu@intel.com>,
Moritz Fischer <mdf@kernel.org>,
linux-fpga@vger.kernel.org
Subject: Re: [PATCH v2] fpga: dfl: afu: convert get_user_pages() --> pin_user_pages()
Date: Sat, 23 May 2020 13:57:17 -0700 [thread overview]
Message-ID: <20200523205717.GA443638@epycbox.lan> (raw)
In-Reply-To: <64aa1494-7570-5319-b096-ea354ff20431@nvidia.com>
On Fri, May 22, 2020 at 06:52:34PM -0700, John Hubbard wrote:
> On 2020-05-19 13:14, John Hubbard wrote:
> > This code was using get_user_pages_fast(), in a "Case 2" scenario
> > (DMA/RDMA), using the categorization from [1]. That means that it's
> > time to convert the get_user_pages_fast() + put_page() calls to
> > pin_user_pages_fast() + unpin_user_pages() calls.
> >
> > There is some helpful background in [2]: basically, this is a small
> > part of fixing a long-standing disconnect between pinning pages, and
> > file systems' use of those pages.
> >
> > [1] Documentation/core-api/pin_user_pages.rst
> >
> > [2] "Explicit pinning of user-space pages":
> > https://lwn.net/Articles/807108/
> >
> > Cc: Xu Yilun <yilun.xu@intel.com>
> > Cc: Wu Hao <hao.wu@intel.com>
> > Cc: Moritz Fischer <mdf@kernel.org>
> > Cc: linux-fpga@vger.kernel.org
> > Signed-off-by: John Hubbard <jhubbard@nvidia.com>
>
>
> Hi Moritz and FPGA developers,
>
> Is this OK? And if so, is it going into your git tree? Or should I
> send it up through a different tree? (I'm new to the FPGA development
> model).
I can take it, sorry for sluggish response.
Cheers,
Moritz
>
>
> thanks,
> --
> John Hubbard
> NVIDIA
>
>
>
> > ---
> >
> > Hi,
> >
> > Changes since v1:
> >
> > Changed the label from "put_pages", to "unpin_pages".
> >
> > thanks,
> > John Hubbard
> > NVIDIA
> > drivers/fpga/dfl-afu-dma-region.c | 19 +++++--------------
> > 1 file changed, 5 insertions(+), 14 deletions(-)
> >
> > diff --git a/drivers/fpga/dfl-afu-dma-region.c b/drivers/fpga/dfl-afu-dma-region.c
> > index 62f924489db5..a31dd3a7e581 100644
> > --- a/drivers/fpga/dfl-afu-dma-region.c
> > +++ b/drivers/fpga/dfl-afu-dma-region.c
> > @@ -16,15 +16,6 @@
> > #include "dfl-afu.h"
> > -static void put_all_pages(struct page **pages, int npages)
> > -{
> > - int i;
> > -
> > - for (i = 0; i < npages; i++)
> > - if (pages[i])
> > - put_page(pages[i]);
> > -}
> > -
> > void afu_dma_region_init(struct dfl_feature_platform_data *pdata)
> > {
> > struct dfl_afu *afu = dfl_fpga_pdata_get_private(pdata);
> > @@ -57,11 +48,11 @@ static int afu_dma_pin_pages(struct dfl_feature_platform_data *pdata,
> > goto unlock_vm;
> > }
> > - pinned = get_user_pages_fast(region->user_addr, npages, FOLL_WRITE,
> > + pinned = pin_user_pages_fast(region->user_addr, npages, FOLL_WRITE,
> > region->pages);
> > if (pinned < 0) {
> > ret = pinned;
> > - goto put_pages;
> > + goto unpin_pages;
> > } else if (pinned != npages) {
> > ret = -EFAULT;
> > goto free_pages;
> > @@ -71,8 +62,8 @@ static int afu_dma_pin_pages(struct dfl_feature_platform_data *pdata,
> > return 0;
> > -put_pages:
> > - put_all_pages(region->pages, pinned);
> > +unpin_pages:
> > + unpin_user_pages(region->pages, pinned);
> > free_pages:
> > kfree(region->pages);
> > unlock_vm:
> > @@ -94,7 +85,7 @@ static void afu_dma_unpin_pages(struct dfl_feature_platform_data *pdata,
> > long npages = region->length >> PAGE_SHIFT;
> > struct device *dev = &pdata->dev->dev;
> > - put_all_pages(region->pages, npages);
> > + unpin_user_pages(region->pages, npages);
> > kfree(region->pages);
> > account_locked_vm(current->mm, npages, false);
> >
>
next prev parent reply other threads:[~2020-05-23 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 20:14 [PATCH v2] fpga: dfl: afu: convert get_user_pages() --> pin_user_pages() John Hubbard
2020-05-23 1:52 ` John Hubbard
2020-05-23 20:57 ` Moritz Fischer [this message]
2020-05-23 21:33 ` John Hubbard
2020-05-25 2:25 ` Wu, Hao
2020-05-25 2:34 ` John Hubbard
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=20200523205717.GA443638@epycbox.lan \
--to=mdf@kernel.org \
--cc=hao.wu@intel.com \
--cc=jhubbard@nvidia.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yilun.xu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox