From: Christoph Hellwig <hch@lst.de>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: axboe@kernel.dk, kbusch@kernel.org, hch@lst.de, sagi@grimberg.me,
martin.petersen@oracle.com,
James.Bottomley@HansenPartnership.com, brauner@kernel.org,
viro@zeniv.linux.org.uk, jack@suse.cz, jaegeuk@kernel.org,
jlayton@kernel.org, chuck.lever@oracle.com, bvanassche@acm.org,
linux-nvme@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
gost.dev@samsung.com, vishak.g@samsung.com,
javier.gonz@samsung.com
Subject: Re: [PATCH v5 1/5] fs, block: refactor enum rw_hint
Date: Thu, 12 Sep 2024 14:53:47 +0200 [thread overview]
Message-ID: <20240912125347.GA28068@lst.de> (raw)
In-Reply-To: <20240910150200.6589-2-joshi.k@samsung.com>
On Tue, Sep 10, 2024 at 08:31:56PM +0530, Kanchan Joshi wrote:
> Rename enum rw_hint to rw_lifetime_hint.
> Change i_write_hint (in inode), bi_write_hint(in bio), and write_hint
> (in request) to use u8 data-type rather than this enum.
>
> This is in preparation to introduce a new write hint type.
The rationale seems a bit sparse. Why is it renamed? Because the
name fits better, because you need the same for something else?
> static void submit_bh_wbc(blk_opf_t opf, struct buffer_head *bh,
> - enum rw_hint hint, struct writeback_control *wbc);
> + u8 hint, struct writeback_control *wbc);
And moving from the enum to an plain integer seems like a bit of a
retrograde step.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org, brauner@kernel.org,
jack@suse.cz, sagi@grimberg.me, martin.petersen@oracle.com,
gost.dev@samsung.com, jlayton@kernel.org, vishak.g@samsung.com,
linux-nvme@lists.infradead.org,
linux-f2fs-devel@lists.sourceforge.net,
James.Bottomley@HansenPartnership.com,
linux-fsdevel@vger.kernel.org, chuck.lever@oracle.com,
javier.gonz@samsung.com, viro@zeniv.linux.org.uk,
linux-scsi@vger.kernel.org, kbusch@kernel.org,
jaegeuk@kernel.org, hch@lst.de, bvanassche@acm.org
Subject: Re: [f2fs-dev] [PATCH v5 1/5] fs, block: refactor enum rw_hint
Date: Thu, 12 Sep 2024 14:53:47 +0200 [thread overview]
Message-ID: <20240912125347.GA28068@lst.de> (raw)
In-Reply-To: <20240910150200.6589-2-joshi.k@samsung.com>
On Tue, Sep 10, 2024 at 08:31:56PM +0530, Kanchan Joshi wrote:
> Rename enum rw_hint to rw_lifetime_hint.
> Change i_write_hint (in inode), bi_write_hint(in bio), and write_hint
> (in request) to use u8 data-type rather than this enum.
>
> This is in preparation to introduce a new write hint type.
The rationale seems a bit sparse. Why is it renamed? Because the
name fits better, because you need the same for something else?
> static void submit_bh_wbc(blk_opf_t opf, struct buffer_head *bh,
> - enum rw_hint hint, struct writeback_control *wbc);
> + u8 hint, struct writeback_control *wbc);
And moving from the enum to an plain integer seems like a bit of a
retrograde step.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-09-12 12:53 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240910151040epcas5p3f47fa7ea37a35f8b44dd9174689e1bb9@epcas5p3.samsung.com>
2024-09-10 15:01 ` [PATCH v5 0/5] data placement hints and FDP Kanchan Joshi
2024-09-10 15:01 ` [f2fs-dev] " Kanchan Joshi
2024-09-10 15:01 ` [PATCH v5 1/5] fs, block: refactor enum rw_hint Kanchan Joshi
2024-09-10 15:01 ` [f2fs-dev] " Kanchan Joshi
2024-09-12 12:53 ` Christoph Hellwig [this message]
2024-09-12 12:53 ` Christoph Hellwig
2024-09-12 15:50 ` Kanchan Joshi
2024-09-12 15:50 ` [f2fs-dev] " Kanchan Joshi
2024-09-12 20:30 ` Bart Van Assche
2024-09-12 20:30 ` [f2fs-dev] " Bart Van Assche via Linux-f2fs-devel
2024-09-13 7:22 ` Kanchan Joshi
2024-09-13 7:22 ` [f2fs-dev] " Kanchan Joshi
2024-09-10 15:01 ` [PATCH v5 2/5] fcntl: rename rw_hint_* to rw_lifetime_hint_* Kanchan Joshi
2024-09-10 15:01 ` [f2fs-dev] " Kanchan Joshi
2024-09-12 12:54 ` Christoph Hellwig
2024-09-12 12:54 ` [f2fs-dev] " Christoph Hellwig
2024-09-12 15:51 ` Kanchan Joshi
2024-09-12 15:51 ` [f2fs-dev] " Kanchan Joshi
2024-09-10 15:01 ` [PATCH v5 3/5] fcntl: add F_{SET/GET}_RW_HINT_EX Kanchan Joshi
2024-09-10 15:01 ` [f2fs-dev] " Kanchan Joshi
2024-09-10 18:48 ` Jens Axboe
2024-09-10 18:48 ` [f2fs-dev] " Jens Axboe
2024-09-11 15:50 ` Kanchan Joshi
2024-09-11 15:50 ` [f2fs-dev] " Kanchan Joshi
2024-09-12 13:01 ` Christoph Hellwig
2024-09-12 13:01 ` [f2fs-dev] " Christoph Hellwig
2024-09-12 15:53 ` Kanchan Joshi
2024-09-12 15:53 ` [f2fs-dev] " Kanchan Joshi
2024-09-12 20:36 ` Bart Van Assche
2024-09-12 20:36 ` [f2fs-dev] " Bart Van Assche via Linux-f2fs-devel
2024-09-13 7:15 ` Kanchan Joshi
2024-09-13 7:15 ` [f2fs-dev] " Kanchan Joshi
2024-09-10 15:01 ` [PATCH v5 4/5] sd: limit to use write life hints Kanchan Joshi
2024-09-10 15:01 ` [f2fs-dev] " Kanchan Joshi
2024-09-12 13:02 ` Christoph Hellwig
2024-09-12 13:02 ` [f2fs-dev] " Christoph Hellwig
2024-09-12 16:31 ` Kanchan Joshi
2024-09-12 16:31 ` [f2fs-dev] " Kanchan Joshi
2024-09-13 8:06 ` Christoph Hellwig
2024-09-13 8:06 ` [f2fs-dev] " Christoph Hellwig
2024-09-16 13:49 ` Kanchan Joshi
2024-09-16 13:49 ` [f2fs-dev] " Kanchan Joshi
2024-09-17 6:20 ` Christoph Hellwig
2024-09-17 6:20 ` [f2fs-dev] " Christoph Hellwig
2024-09-17 16:03 ` Kanchan Joshi
2024-09-17 16:03 ` [f2fs-dev] " Kanchan Joshi
2024-09-17 17:00 ` Kanchan Joshi
2024-09-17 17:00 ` [f2fs-dev] " Kanchan Joshi
2024-09-18 6:42 ` Christoph Hellwig
2024-09-18 6:42 ` [f2fs-dev] " Christoph Hellwig
2024-09-18 8:12 ` Kanchan Joshi
2024-09-18 8:12 ` [f2fs-dev] " Kanchan Joshi
2024-09-18 12:01 ` Christoph Hellwig
2024-09-18 12:01 ` [f2fs-dev] " Christoph Hellwig
2024-09-24 9:24 ` Kanchan Joshi
2024-09-24 9:24 ` [f2fs-dev] " Kanchan Joshi
2024-09-24 9:28 ` Christoph Hellwig
2024-09-24 9:28 ` [f2fs-dev] " Christoph Hellwig
2024-09-10 15:02 ` [PATCH v5 5/5] nvme: enable FDP support Kanchan Joshi
2024-09-10 15:02 ` [f2fs-dev] " Kanchan Joshi
2025-01-29 0:56 ` [f2fs-dev] [PATCH v5 0/5] data placement hints and FDP patchwork-bot+f2fs
2025-01-29 0:56 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
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=20240912125347.GA28068@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=bvanassche@acm.org \
--cc=chuck.lever@oracle.com \
--cc=gost.dev@samsung.com \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=javier.gonz@samsung.com \
--cc=jlayton@kernel.org \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sagi@grimberg.me \
--cc=viro@zeniv.linux.org.uk \
--cc=vishak.g@samsung.com \
/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.