From: Pavel Tatashin <pasha.tatashin@soleen.com>
To: Tyler Hicks <tyhicks@linux.microsoft.com>
Cc: Zhansaya Bagdauletkyzy <zhansayabagdaulet@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
linux-kselftest@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] selftests: vm: add KSM merging time test
Date: Fri, 20 Aug 2021 13:19:23 -0400 [thread overview]
Message-ID: <CA+CK2bCfqGsZKr5Fh3pRC6NcyJExxjrg7C6NxQWvZbVa_PeK=Q@mail.gmail.com> (raw)
In-Reply-To: <20210819162953.GN5469@sequoia>
On Thu, Aug 19, 2021 at 12:29 PM Tyler Hicks
<tyhicks@linux.microsoft.com> wrote:
>
> On 2021-08-19 21:33:41, Zhansaya Bagdauletkyzy wrote:
> > Add ksm_merge_time() function to determine speed and time needed for
> > merging. The total spent time is shown in seconds while speed is
> > in MiB/s. User must specify the size of duplicated memory area (in MiB)
> > before running the test.
> >
> > The test is run as follows: ./ksm_tests -P -s 100
> > The output:
> > Total size: 100 MiB
> > Total time: 0.201106786 s
> > Average speed: 497.248 MiB/s
> >
> > Signed-off-by: Zhansaya Bagdauletkyzy <zhansayabagdaulet@gmail.com>
> > ---
> > v2 -> v3:
> > - no changes
>
> There were no changes to this patch since v2 so my previous review still
> stands:
>
> Reviewed-by: Tyler Hicks <tyhicks@linux.microsoft.com>
Thank you for addressing my comments in v2.
Reviewed-by: Pavel Tatashin <pasha.tatashin@soleen.com>
next prev parent reply other threads:[~2021-08-20 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 15:33 [PATCH v3 0/2] add KSM performance tests Zhansaya Bagdauletkyzy
2021-08-19 15:33 ` [PATCH v3 1/2] selftests: vm: add KSM merging time test Zhansaya Bagdauletkyzy
2021-08-19 16:29 ` Tyler Hicks
2021-08-20 17:19 ` Pavel Tatashin [this message]
2021-08-19 15:33 ` [PATCH v3 2/2] selftests: vm: add COW time test for KSM pages Zhansaya Bagdauletkyzy
2021-08-19 16:31 ` Tyler Hicks
2021-08-20 17:20 ` Pavel Tatashin
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='CA+CK2bCfqGsZKr5Fh3pRC6NcyJExxjrg7C6NxQWvZbVa_PeK=Q@mail.gmail.com' \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tyhicks@linux.microsoft.com \
--cc=zhansayabagdaulet@gmail.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;
as well as URLs for NNTP newsgroup(s).