From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org
Subject: [PATCHSET 0/2] Optimize block_device utilization
Date: Fri, 14 Apr 2023 07:48:46 -0600 [thread overview]
Message-ID: <20230414134848.91563-1-axboe@kernel.dk> (raw)
Hi,
First is just a prep patch that moves struct device, which is quite the
pig, out of line in block_device, and then shuffles a few fields for
better layout. It also saves 16 bytes of space in there while at it.
Second patch caches the bdev->disk->fops->submit_bio state in the bdev,
so we can avoid this long dependent memory load chain in the fast
path.
--
Jens Axboe
next reply other threads:[~2023-04-14 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 13:48 Jens Axboe [this message]
2023-04-14 13:48 ` [PATCH 1/2] block: re-arrange the struct block_device fields for better layout Jens Axboe
2023-04-16 5:51 ` Christoph Hellwig
2023-04-16 19:01 ` Jens Axboe
2023-04-14 13:48 ` [PATCH 2/2] block: store bdev->bd_disk->fops->submit_bio state in bdev Jens Axboe
2023-04-15 2:43 ` Damien Le Moal
2023-04-15 3:41 ` Jens Axboe
2023-04-16 5:53 ` Christoph Hellwig
2023-04-16 18:59 ` 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=20230414134848.91563-1-axboe@kernel.dk \
--to=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 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).