From: Peter Xu <peterx@redhat.com>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
Jerome Glisse <jglisse@redhat.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
linux-mm@kvack.org, Zi Yan <zi.yan@cs.rutgers.edu>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
linux-kselftest@vger.kernel.org, Shaohua Li <shli@fb.com>,
Andrea Arcangeli <aarcange@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/3] userfaultfd: selftest: cleanup help messages
Date: Sun, 30 Sep 2018 14:34:01 +0800 [thread overview]
Message-ID: <20180930063401.GA18728@xz-x1> (raw)
In-Reply-To: <20180929102811.GA6429@rapoport-lnx>
On Sat, Sep 29, 2018 at 01:28:12PM +0300, Mike Rapoport wrote:
[...]
> > +const char *examples =
> > + "# 100MiB 99999 bounces\n"
> > + "./userfaultfd anon 100 99999\n"
> > + "\n"
> > + "# 1GiB 99 bounces\n"
> > + "./userfaultfd anon 1000 99\n"
> > + "\n"
> > + "# 10MiB-~6GiB 999 bounces, continue forever unless an error triggers\n"
> > + "while ./userfaultfd anon $[RANDOM % 6000 + 10] 999; do true; done\n"
> > + "\n";
>
> While at it, can you please update the examples to include other test
> types?
Sure thing.
Thanks for the quick review!
Regards,
--
Peter Xu
next prev parent reply other threads:[~2018-09-30 6:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 8:43 [PATCH 0/3] userfaultfd: selftests: cleanups and trivial fixes Peter Xu
2018-09-29 8:43 ` [PATCH 1/3] userfaultfd: selftest: cleanup help messages Peter Xu
2018-09-29 10:28 ` Mike Rapoport
2018-09-30 6:34 ` Peter Xu [this message]
2018-09-29 8:43 ` [PATCH 2/3] userfaultfd: selftest: generalize read and poll Peter Xu
2018-09-29 10:31 ` Mike Rapoport
2018-09-29 8:43 ` [PATCH 3/3] userfaultfd: selftest: recycle lock threads first Peter Xu
2018-09-29 10:32 ` Mike Rapoport
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=20180930063401.GA18728@xz-x1 \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dgilbert@redhat.com \
--cc=jglisse@redhat.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=shli@fb.com \
--cc=shuah@kernel.org \
--cc=zi.yan@cs.rutgers.edu \
/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).