From: Daniel Borkmann <daniel@iogearbox.net>
To: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>,
Bjorn Topel <bjorn.topel@intel.com>,
Magnus Karlsson <magnus.karlsson@intel.com>,
netdev@vger.kernel.org, Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH v2] xsk: share the mmap_sem for page pinning
Date: Mon, 11 Feb 2019 20:53:37 +0100 [thread overview]
Message-ID: <ec544ae4-4671-de96-69c2-2f438f048a83@iogearbox.net> (raw)
In-Reply-To: <20190211161529.uskq5ca7y3j5522i@linux-r8p5>
On 02/11/2019 05:15 PM, Davidlohr Bueso wrote:
> Holding mmap_sem exclusively for a gup() is an overkill.
> Lets share the lock and replace the gup call for gup_longterm(),
> as it is better suited for the lifetime of the pinning.
>
> Cc: David S. Miller <davem@davemloft.net>
> Cc: Bjorn Topel <bjorn.topel@intel.com>
> Cc: Magnus Karlsson <magnus.karlsson@intel.com>
> CC: netdev@vger.kernel.org
> Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
Applied, thanks!
next prev parent reply other threads:[~2019-02-11 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 5:37 [PATCH -tip 0/2] more get_user_pages mmap_sem cleanups Davidlohr Bueso
2019-02-07 5:37 ` [PATCH 1/2] xsk: do not use mmap_sem Davidlohr Bueso
2019-02-07 7:43 ` Björn Töpel
2019-02-11 15:33 ` Daniel Borkmann
2019-02-11 16:37 ` Dan Williams
2019-02-11 17:16 ` Weiny, Ira
2019-02-11 16:15 ` [PATCH v2] xsk: share the mmap_sem for page pinning Davidlohr Bueso
2019-02-11 16:21 ` Björn Töpel
2019-02-11 19:53 ` Daniel Borkmann [this message]
2019-02-07 5:37 ` [PATCH 2/2] MIPS/c-r4k: do no use mmap_sem for gup_fast() Davidlohr Bueso
2019-02-07 19:00 ` Paul Burton
2019-02-07 19:25 ` Davidlohr Bueso
2019-02-07 5:50 ` [PATCH -tip 0/2] more get_user_pages mmap_sem cleanups Davidlohr Bueso
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=ec544ae4-4671-de96-69c2-2f438f048a83@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=akpm@linux-foundation.org \
--cc=bjorn.topel@intel.com \
--cc=davem@davemloft.net \
--cc=dbueso@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.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).