From: Christoph Hellwig <hch@infradead.org>
To: Jiaming Li <lijiaming3@xiaomi.corp-partner.google.com>
Cc: alim.akhtar@samsung.com, avri.altman@wdc.com, bvanassche@acm.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
lijiaming3 <lijiaming3@xiaomi.com>
Subject: Re: [RESEND PATCH 0/4] Implement File-Based optimization functionality
Date: Wed, 2 Nov 2022 01:47:00 -0700 [thread overview]
Message-ID: <Y2IuhG8nBJj0F1fd@infradead.org> (raw)
In-Reply-To: <20221102053058.21021-1-lijiaming3@xiaomi.corp-partner.google.com>
On Wed, Nov 02, 2022 at 01:30:54PM +0800, Jiaming Li wrote:
> 1) The host let the device know of lba range(s) of interest. Those
> ranges are typically associated with a specific file. One can
> obtain it from the iNode of the file and some offset calculations.
This is completely and utter madness. Files are a logic concept, that
is non-unique (reflinks, snapshot) and can change at any time
(defragmentation, GC, dedup). Whoever came up with this scheme is on
crack and the it has no business being in the Linux kernel
NAK.
next prev parent reply other threads:[~2022-11-02 8:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 5:30 [RESEND PATCH 0/4] Implement File-Based optimization functionality Jiaming Li
2022-11-02 5:30 ` [RESEND PATCH 1/4] scsi:ufs:remove sanity check Jiaming Li
2022-11-02 7:23 ` Avri Altman
2022-11-02 5:30 ` [RESEND PATCH 2/4] scsi:ufs:add File-Based Optimization descriptor Jiaming Li
2022-11-02 7:46 ` Avri Altman
2022-11-02 5:30 ` [RESEND PATCH 3/4] scsi:ufs:add FBO module Jiaming Li
2022-11-02 8:11 ` Avri Altman
2022-11-14 21:21 ` kernel test robot
2022-11-02 5:30 ` [RESEND PATCH 4/4] scsi:ufs:add fbo functionality Jiaming Li
2022-11-02 8:53 ` Avri Altman
2022-11-02 20:26 ` kernel test robot
2022-11-02 8:47 ` Christoph Hellwig [this message]
2022-11-03 6:11 ` [RESEND PATCH 0/4] Implement File-Based optimization functionality Juhyung Park
2022-11-04 12:37 ` Matias Bjørling
2022-11-05 5:22 ` Juhyung Park
2022-11-09 12:31 ` Christoph Hellwig
2022-11-02 15:24 ` Bart Van Assche
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=Y2IuhG8nBJj0F1fd@infradead.org \
--to=hch@infradead.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=lijiaming3@xiaomi.com \
--cc=lijiaming3@xiaomi.corp-partner.google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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