From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Keith Busch <keith.busch@intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCHv3 4/6] tools/gup_benchmark: Allow user specified file
Date: Tue, 2 Oct 2018 14:03:38 +0300 [thread overview]
Message-ID: <20181002110338.fw7d4jv5e5a6yd4v@black.fi.intel.com> (raw)
In-Reply-To: <20180921223956.3485-5-keith.busch@intel.com>
On Fri, Sep 21, 2018 at 10:39:54PM +0000, Keith Busch wrote:
> The gup benchmark by default maps anonymous memory. This patch allows a
> user to specify a file to map, providing a means to test various
> file backings, like device and filesystem DAX.
>
> Cc: Kirill Shutemov <kirill.shutemov@linux.intel.com>
> Cc: Dave Hansen <dave.hansen@intel.com>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Keith Busch <keith.busch@intel.com>
> ---
> tools/testing/selftests/vm/gup_benchmark.c | 19 ++++++++++++++++---
> 1 file changed, 16 insertions(+), 3 deletions(-)
>
> diff --git a/tools/testing/selftests/vm/gup_benchmark.c b/tools/testing/selftests/vm/gup_benchmark.c
> index b2082df8beb4..f2c99e2436f8 100644
> --- a/tools/testing/selftests/vm/gup_benchmark.c
> +++ b/tools/testing/selftests/vm/gup_benchmark.c
> @@ -33,9 +33,12 @@ int main(int argc, char **argv)
> unsigned long size = 128 * MB;
> int i, fd, opt, nr_pages = 1, thp = -1, repeats = 1, write = 0;
> int cmd = GUP_FAST_BENCHMARK;
> + int file_map = -1;
> + int flags = MAP_ANONYMOUS | MAP_PRIVATE;
> + char *file = NULL;
> char *p;
>
> - while ((opt = getopt(argc, argv, "m:r:n:tTLU")) != -1) {
> + while ((opt = getopt(argc, argv, "m:r:n:f:tTLU")) != -1) {
> switch (opt) {
> case 'm':
> size = atoi(optarg) * MB;
> @@ -61,11 +64,22 @@ int main(int argc, char **argv)
> case 'w':
> write = 1;
> break;
> + case 'f':
> + file = optarg;
> + flags &= ~(MAP_PRIVATE | MAP_ANONYMOUS);
> + flags |= MAP_SHARED;
Why do we want to assume shared mapping if a file is passed? Private-file
mapping is also valid target for the benchmark.
Maybe a separate option for shared? It would keep options more independent.
BTW, we can make a default file /dev/zero and don't have MAP_ANONYMOUS in
the flags: private mapping of /dev/zero would produce anonymous mapping.
No need in masking out MAP_ANONYMOUS on -f and no branch on 'if (file)'
below.
> + break;
> default:
> return -1;
> }
> }
>
> + if (file) {
> + file_map = open(file, O_RDWR|O_CREAT);
> + if (file_map < 0)
> + perror("open"), exit(file_map);
> + }
> +
> gup.nr_pages_per_call = nr_pages;
> gup.flags = write;
>
> @@ -73,8 +87,7 @@ int main(int argc, char **argv)
> if (fd == -1)
> perror("open"), exit(1);
>
> - p = mmap(NULL, size, PROT_READ | PROT_WRITE,
> - MAP_ANONYMOUS | MAP_PRIVATE, -1, 0);
> + p = mmap(NULL, size, PROT_READ | PROT_WRITE, flags, file_map, 0);
> if (p == MAP_FAILED)
> perror("mmap"), exit(1);
> gup.addr = (unsigned long)p;
> --
> 2.14.4
>
--
Kirill A. Shutemov
next prev parent reply other threads:[~2018-10-02 11:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 22:39 [PATCHv3 0/6] mm: faster get user pages Keith Busch
2018-09-21 22:39 ` [PATCHv3 1/6] mm/gup_benchmark: Time put_page Keith Busch
2018-10-02 10:54 ` Kirill A. Shutemov
2018-09-21 22:39 ` [PATCHv3 2/6] mm/gup_benchmark: Add additional pinning methods Keith Busch
2018-10-02 10:56 ` Kirill A. Shutemov
2018-09-21 22:39 ` [PATCHv3 3/6] tools/gup_benchmark: Fix 'write' flag usage Keith Busch
2018-10-02 10:57 ` Kirill A. Shutemov
2018-09-21 22:39 ` [PATCHv3 4/6] tools/gup_benchmark: Allow user specified file Keith Busch
2018-10-02 11:03 ` Kirill A. Shutemov [this message]
2018-09-21 22:39 ` [PATCHv3 5/6] tools/gup_benchmark: Add parameter for hugetlb Keith Busch
2018-10-02 11:05 ` Kirill A. Shutemov
2018-09-21 22:39 ` [PATCHv3 6/6] mm/gup: Cache dev_pagemap while pinning pages Keith Busch
2018-10-02 11:26 ` Kirill A. Shutemov
2018-10-02 15:49 ` Dave Hansen
2018-10-02 16:05 ` Keith Busch
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=20181002110338.fw7d4jv5e5a6yd4v@black.fi.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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