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, linux-fsdevel@vger.kernel.org,
	linux-mm@vger.kernel.org
Subject: Re: [PATCH] block: Improve read ahead size for rotational devices
Date: Tue, 29 Jul 2025 16:58:47 +0900	[thread overview]
Message-ID: <dd34e42f-4451-40cf-ae14-ba5da2efcc49@kernel.org> (raw)
In-Reply-To: <20250616062856.1629897-1-dlemoal@kernel.org>

On 6/16/25 15:28, Damien Le Moal wrote:
> For a device that does not advertize an optimal I/O size, the function
> blk_apply_bdi_limits() defaults to an initial setting of the ra_pages
> field of struct backing_dev_info to VM_READAHEAD_PAGES, that is, 128 KB.
> 
> This low I/O size value is far from being optimal for hard-disk devices:
> when reading files from multiple contexts using buffered I/Os, the seek
> overhead between the small read commands generated to read-ahead
> multiple files will significantly limit the performance that can be
> achieved.
> 
> This fact applies to all ATA devices as ATA does not define an optimal
> I/O size and the SCSI SAT specification does not define a default value
> to expose to the host.
> 
> Modify blk_apply_bdi_limits() to use a device max_sectors limit to
> calculate the ra_pages field of struct backing_dev_info, when the device
> is a rotational one (BLK_FEAT_ROTATIONAL feature is set). For a SCSI
> disk, this defaults to 2560 KB, which significantly improve performance
> for buffered reads. Using XFS and sequentially reading randomly selected
> (large) files stored on a SATA HDD, the maximum throughput achieved with
> 8 readers reading files with 1MB buffered I/Os increases from 122 MB/s
> to 167 MB/s (+36%). The improvement is even larger when reading files
> using 128 KB buffered I/Os, with a throughput increasing from 57 MB/s to
> 165 MB/s (+189%).
> 
> Signed-off-by: Damien Le Moal <dlemoal@kernel.org>

Jens,

Ping ? This is reviewed. Did it got lost ? Or will it be part of a different PR ?

-- 
Damien Le Moal
Western Digital Research

  parent reply	other threads:[~2025-07-29  7:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  6:28 [PATCH] block: Improve read ahead size for rotational devices Damien Le Moal
2025-06-16 21:24 ` Martin K. Petersen
2025-06-16 22:45   ` Damien Le Moal
2025-06-17  5:10   ` Christoph Hellwig
2025-06-17  5:09 ` Christoph Hellwig
2025-06-17  6:58 ` John Garry
2025-07-29  7:58 ` Damien Le Moal [this message]
2025-07-29 12:27 ` 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=dd34e42f-4451-40cf-ae14-ba5da2efcc49@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@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.