From: Mike Rapoport <rppt@kernel.org>
To: Yuanchu Xie <yuanchu@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Yang Shi <shy828301@gmail.com>, Zach O'Keefe <zokeefe@google.com>,
Peter Xu <peterx@redhat.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Matthew Wilcox <willy@infradead.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] mm: pagemap: restrict pagewalk to the requested range
Date: Tue, 16 May 2023 10:45:05 +0300 [thread overview]
Message-ID: <ZGM0gegQkvrQtq49@kernel.org> (raw)
In-Reply-To: <20230515172608.3558391-1-yuanchu@google.com>
On Tue, May 16, 2023 at 01:26:08AM +0800, Yuanchu Xie wrote:
> The pagewalk in pagemap_read reads one PTE past the end of the requested
> range, and stops when the buffer runs out of space. While it produces
> the right result, the extra read is unnecessary and less performant.
>
> I timed the following command before and after this patch:
> dd count=100000 if=/proc/self/pagemap of=/dev/null
> The results are consistently within 0.001s across 5 runs.
>
> Before:
> 100000+0 records in
> 100000+0 records out
> 51200000 bytes (51 MB) copied, 0.0763159 s, 671 MB/s
>
> real 0m0.078s
> user 0m0.012s
> sys 0m0.065s
>
> After:
> 100000+0 records in
> 100000+0 records out
> 51200000 bytes (51 MB) copied, 0.0487928 s, 1.0 GB/s
>
> real 0m0.050s
> user 0m0.011s
> sys 0m0.039s
>
> Signed-off-by: Yuanchu Xie <yuanchu@google.com>
Acked-by: Mike Rapoport (IBM) <rppt@kernel.org>
> ---
> fs/proc/task_mmu.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
> index 420510f6a545..6259dd432eeb 100644
> --- a/fs/proc/task_mmu.c
> +++ b/fs/proc/task_mmu.c
> @@ -1689,23 +1689,23 @@ static ssize_t pagemap_read(struct file *file, char __user *buf,
> /* watch out for wraparound */
> start_vaddr = end_vaddr;
> if (svpfn <= (ULONG_MAX >> PAGE_SHIFT)) {
> + unsigned long end;
> +
> ret = mmap_read_lock_killable(mm);
> if (ret)
> goto out_free;
> start_vaddr = untagged_addr_remote(mm, svpfn << PAGE_SHIFT);
> mmap_read_unlock(mm);
> +
> + end = start_vaddr + ((count / PM_ENTRY_BYTES) << PAGE_SHIFT);
> + if (end >= start_vaddr && end < mm->task_size)
> + end_vaddr = end;
> }
>
> /* Ensure the address is inside the task */
> if (start_vaddr > mm->task_size)
> start_vaddr = end_vaddr;
>
> - /*
> - * The odds are that this will stop walking way
> - * before end_vaddr, because the length of the
> - * user buffer is tracked in "pm", and the walk
> - * will stop when we hit the end of the buffer.
> - */
> ret = 0;
> while (count && (start_vaddr < end_vaddr)) {
> int len;
> --
> 2.40.1.606.ga4b1b128d6-goog
>
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2023-05-16 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 17:26 Yuanchu Xie
2023-05-15 22:05 ` Peter Xu
2023-05-16 7:45 ` Mike Rapoport [this message]
2023-05-16 17:10 ` Yang Shi
2023-05-21 23:55 ` David Rientjes
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=ZGM0gegQkvrQtq49@kernel.org \
--to=rppt@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=peterx@redhat.com \
--cc=shy828301@gmail.com \
--cc=willy@infradead.org \
--cc=yuanchu@google.com \
--cc=zokeefe@google.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