All of lore.kernel.org
 help / color / mirror / Atom feed
From: 常凤楠 <changfengnan@vivo.com>
To: "tytso@mit.edu" <tytso@mit.edu>,
	"jaegeuk@kernel.org" <jaegeuk@kernel.org>,
	"ebiggers@kernel.org" <ebiggers@kernel.org>,
	"satyat@google.com" <satyat@google.com>
Cc: "linux-fscrypt@vger.kernel.org" <linux-fscrypt@vger.kernel.org>
Subject: why fscrypt_mergeable_bio use logical block number?
Date: Fri, 15 Apr 2022 08:18:11 +0000	[thread overview]
Message-ID: <KL1PR0601MB4003998B841513BCAA386ADEBBEE9@KL1PR0601MB4003.apcprd06.prod.outlook.com> (raw)

Hi:
	When I dig into a problem, I found: bio merge may reduce a lot when enable inlinecrypt, the root cause is fscrypt_mergeable_bio use logical block number rather than physical block number. I had read the UFSHCI, but not see any description about why data unit number shoud use logical block number. I want to know why, Is the anyone can explain this?

Thanks.
Fengnan Chang.

             reply	other threads:[~2022-04-15  8:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15  8:18 常凤楠 [this message]
2022-04-15 18:49 ` why fscrypt_mergeable_bio use logical block number? Eric Biggers
2022-04-17  2:34   ` 常凤楠
2022-04-18  7:25     ` Eric Biggers

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=KL1PR0601MB4003998B841513BCAA386ADEBBEE9@KL1PR0601MB4003.apcprd06.prod.outlook.com \
    --to=changfengnan@vivo.com \
    --cc=ebiggers@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=satyat@google.com \
    --cc=tytso@mit.edu \
    /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.