From: Bart Van Assche <bvanassche@acm.org>
To: Theodore Tso <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>,
linux-f2fs-devel@lists.sourceforge.net,
Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Akilesh Kailash <akailash@google.com>,
Christian Brauner <christian@brauner.io>
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: another way to set large folio by remembering inode number
Date: Tue, 26 May 2026 18:15:24 -0700 [thread overview]
Message-ID: <426a9687-c39e-4ac8-a406-d5e2198f01b0@acm.org> (raw)
In-Reply-To: <ybmbjekuvzmaw4hmlxd7nxs546dqtwmxqxwyali74d6m3u7tat@b4q3japqnhrl>
On 5/26/26 6:42 AM, Theodore Tso wrote:
> 2. Host Controller Hardware Limits (UFSHCI)
>
> Transfer Queue Depth: A UFS controller supports a predefined
> number of outstanding task request entries. This is often
> hard-capped at 32 concurrent transfer requests (slots) by the
> doorbell register array.
The above information comes from the UFSHCI 3 standard. Jaegeuk's test
setup has an UFSHCI 4.0 controller that supports one submission queue
per CPU and also one completion queue per CPU. This is an architecture
that is very similar but not identical to NVMe. Jaegeuk, please correct
me if I got anything wrong.
Bart.
next prev parent reply other threads:[~2026-05-27 1:15 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 13:45 [PATCH] " Jaegeuk Kim
2026-04-10 1:16 ` [PATCH v2] " Jaegeuk Kim
2026-04-14 8:02 ` Christoph Hellwig
2026-04-15 16:44 ` Jaegeuk Kim
2026-04-15 17:15 ` Matthew Wilcox
2026-04-15 22:02 ` Jaegeuk Kim
2026-04-15 23:49 ` Darrick J. Wong
2026-04-16 1:19 ` Jaegeuk Kim
2026-05-21 8:51 ` Christoph Hellwig
2026-05-21 15:57 ` Theodore Tso
2026-05-21 17:42 ` Matthew Wilcox
2026-05-22 3:59 ` Jaegeuk Kim
2026-05-22 12:55 ` Matthew Wilcox
2026-05-22 14:04 ` [f2fs-dev] " Jaegeuk Kim
2026-05-25 5:34 ` Christoph Hellwig
2026-05-26 1:21 ` Jaegeuk Kim
2026-05-26 2:31 ` Matthew Wilcox
2026-05-26 3:47 ` Jaegeuk Kim
2026-05-27 6:33 ` Christoph Hellwig
2026-05-27 6:26 ` Christoph Hellwig
2026-05-27 15:42 ` Jaegeuk Kim
2026-05-25 5:34 ` Christoph Hellwig
2026-05-22 3:32 ` [f2fs-dev] " Jaegeuk Kim
2026-05-22 3:53 ` Eric Biggers
2026-05-22 4:02 ` Jaegeuk Kim
2026-05-22 10:01 ` Christian Brauner
2026-05-22 14:11 ` Theodore Tso
2026-05-22 17:08 ` Jaegeuk Kim
2026-05-22 22:41 ` Theodore Tso
2026-05-26 1:10 ` Jaegeuk Kim
2026-05-26 2:35 ` Matthew Wilcox
2026-05-26 3:34 ` Jaegeuk Kim
2026-05-26 3:35 ` Randy Dunlap
2026-05-26 4:12 ` Jaegeuk Kim
2026-05-26 13:42 ` Theodore Tso
2026-05-26 16:14 ` Bart Van Assche
2026-05-27 6:28 ` Christoph Hellwig
2026-05-27 15:59 ` Jaegeuk Kim
2026-05-29 5:36 ` Christoph Hellwig
2026-05-31 0:12 ` Jaegeuk Kim
2026-05-31 5:28 ` Barry Song
2026-06-01 1:52 ` Jaegeuk Kim
2026-05-26 21:52 ` Jaegeuk Kim
2026-05-27 1:21 ` Theodore Tso
2026-05-27 2:43 ` Jaegeuk Kim
2026-05-27 3:30 ` Matthew Wilcox
2026-05-27 15:39 ` Jaegeuk Kim
2026-05-27 6:31 ` Christoph Hellwig
2026-05-27 1:15 ` Bart Van Assche [this message]
2026-05-28 19:36 ` Matthew Wilcox
2026-05-31 0:35 ` Jaegeuk Kim
2026-05-25 5:37 ` Christoph Hellwig
2026-05-22 9:59 ` Christian Brauner
2026-04-15 16:41 ` Jaegeuk Kim
2026-04-17 0:58 ` [f2fs-dev] " Chao Yu
2026-04-17 16:54 ` Jaegeuk Kim
2026-04-18 1:08 ` Chao Yu
2026-04-18 1:11 ` Chao Yu
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=426a9687-c39e-4ac8-a406-d5e2198f01b0@acm.org \
--to=bvanassche@acm.org \
--cc=akailash@google.com \
--cc=christian@brauner.io \
--cc=hch@infradead.org \
--cc=jaegeuk@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tytso@mit.edu \
--cc=willy@infradead.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
Powered by JetHome