public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Edward Liaw via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Cc: kernel-team@android.com
Subject: [LTP] [PATCH v7 0/1] mmapstress01: refactor to ltp framework
Date: Thu, 27 Oct 2022 21:58:07 +0000	[thread overview]
Message-ID: <20221027215808.4126148-1-edliaw@google.com> (raw)

v6->v7:
* clean up pattern option
* always print configuration info message

v5->v6:
* revert pidarray removal because children use the array index to
determine read/write locations
* add option to specify pattern for reproducibility
* set default nprocs to ncpus with range between 1-20
* remove more comments

v4->v5:
* reformat top level comment to docparse format
* reduce amount of verbose comments
* clean up file size bounds definitions
* make finished variable volatile for >1 retries
* remove unnecessary pidarray because offloaded to test harness
* remove unnecessary sig blocks

v3->v4:
* squash previous changes
* set defaults of nprocs=20 and max_runtime=12
* clean up comments
* return TBROK instead of TFAIL for unexpected failures

v2->v3:
* apply make check lint suggestions
* refactor cleanup
* use SAFE_FORK
* update license

v1->v2:
* clean up formatting
* remove accidental change to header comment
* use SAFE_MMAP

v0->v1:
* use tst_test framework
* use FILE_OFFSET_BITS=64 instead of LARGE_FILE
* use safe macros

Edward Liaw (1):
  mmapstress01: refactor to tst_test framework

 testcases/kernel/mem/mmapstress/Makefile      |   2 +
 .../kernel/mem/mmapstress/mmapstress01.c      | 886 +++++-------------
 2 files changed, 261 insertions(+), 627 deletions(-)

-- 
2.38.1.273.g43a17bfeac-goog


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2022-10-27 21:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 21:58 Edward Liaw via ltp [this message]
2022-10-27 21:58 ` [LTP] [PATCH v7 1/1] mmapstress01: refactor to tst_test framework Edward Liaw via ltp
2022-11-08 10:49   ` Richard Palethorpe
2022-11-08 11:19     ` Richard Palethorpe
2022-11-11 16:53       ` Petr Vorel
2022-11-11 17:07         ` Petr Vorel
2022-11-14 10:00           ` Richard Palethorpe
2022-11-14  9:44         ` Richard Palethorpe
2022-11-14 10:50         ` Cyril Hrubis
2022-11-14 14:17           ` Petr Vorel

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=20221027215808.4126148-1-edliaw@google.com \
    --to=ltp@lists.linux.it \
    --cc=edliaw@google.com \
    --cc=kernel-team@android.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