All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: linux-block@vger.kernel.org
Cc: yukuai3@huawei.com, shinichiro.kawasaki@wdc.com,
	yi.zhang@redhat.com, bvanassche@acm.org, gjoyce@ibm.com
Subject: [PATCHv2 blktests 0/2] throtl: fix IO block-size and race while submitting IO
Date: Wed, 18 Dec 2024 19:13:20 +0530	[thread overview]
Message-ID: <20241218134326.2164105-1-nilay@linux.ibm.com> (raw)

Hi,

The first patch fixes the IO block-size used for submitting IO depending
on the throttle device max-sectors settings.

The second patch fixes the potential race condition between submitting IO
and setting PID of the background IO process to cgroup.procs.

Changes from v1:
    - Use $BASHPID to write the child sub-shell PID into cgroup.procs
      (Shinichiro Kawasaki)
    - Link to v1: https://lore.kernel.org/all/20241217131440.1980151-1-nilay@linux.ibm.com/

Nilay Shroff (2):
  throtl/002: calculate block-size based on device max-sectors setting
  throtl: fix the race between submitting IO and setting cgroup.procs

 tests/throtl/002 | 14 ++++++++++----
 tests/throtl/004 |  7 ++-----
 tests/throtl/005 |  7 ++-----
 tests/throtl/rc  | 11 ++++++-----
 4 files changed, 20 insertions(+), 19 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-12-18 13:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18 13:43 Nilay Shroff [this message]
2024-12-18 13:43 ` [PATCHv2 blktests 1/2] throtl/002: calculate block-size based on device max-sectors setting Nilay Shroff
2024-12-26  7:30   ` Yi Zhang
2024-12-18 13:43 ` [PATCHv2 blktests 2/2] throtl: fix the race between submitting IO and setting cgroup.procs Nilay Shroff
2024-12-25  2:55   ` Yu Kuai
2024-12-24  8:26 ` [PATCHv2 blktests 0/2] throtl: fix IO block-size and race while submitting IO Shinichiro Kawasaki
2025-01-16 11:22   ` Nilay Shroff
2025-01-17  0:35     ` Shinichiro Kawasaki

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=20241218134326.2164105-1-nilay@linux.ibm.com \
    --to=nilay@linux.ibm.com \
    --cc=bvanassche@acm.org \
    --cc=gjoyce@ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=yi.zhang@redhat.com \
    --cc=yukuai3@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.