All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: [PATCH 0/3] Some null_blk cleanups
Date: Thu, 11 Apr 2024 17:54:59 +0900	[thread overview]
Message-ID: <20240411085502.728558-1-dlemoal@kernel.org> (raw)

3 patches to cleanup null_blk main code and improve zone device support.
With the last 2 patches, some performance improvements (up to +1.7%) can
be measured for a null zoned device with no zone resource limits. The
maximum IOPS measured with zone write plugging with a multi-stream 4K
sequential write workload (32 jobs) is:

Before patches:
 - mq-deadline: 596 KIOPS
 - none: 2406 KIOPS

With patches applied:
 - mq-deadline: 600 KIOPS
 - none: 2447 KIOPS

Overall, there is no functional change.

Damien Le Moal (3):
  null_blk: Have all null_handle_xxx() return a blk_status_t
  null_blk: Do zone resource management only if necessary
  null_blk: Simplify null_zone_write()

 drivers/block/null_blk/main.c  |  18 +-
 drivers/block/null_blk/zoned.c | 343 +++++++++++++++++----------------
 2 files changed, 187 insertions(+), 174 deletions(-)

-- 
2.44.0


             reply	other threads:[~2024-04-11  8:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  8:54 Damien Le Moal [this message]
2024-04-11  8:55 ` [PATCH 1/3] null_blk: Have all null_handle_xxx() return a blk_status_t Damien Le Moal
2024-04-11 12:37   ` Nitesh Shetty
2024-04-15 20:59   ` Chaitanya Kulkarni
2024-04-17  9:42   ` Johannes Thumshirn
2024-04-11  8:55 ` [PATCH 2/3] null_blk: Do zone resource management only if necessary Damien Le Moal
2024-04-11  8:55 ` [PATCH 3/3] null_blk: Simplify null_zone_write() Damien Le Moal
2024-04-17  9:42   ` Johannes Thumshirn
2024-04-17 14:45 ` [PATCH 0/3] Some null_blk cleanups Jens Axboe

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=20240411085502.728558-1-dlemoal@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    /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.