From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"colyli@suse.de" <colyli@suse.de>,
"kent.overstreet@gmail.com" <kent.overstreet@gmail.com>,
"agk@redhat.com" <agk@redhat.com>,
"snitzer@kernel.org" <snitzer@kernel.org>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"song@kernel.org" <song@kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Subject: Re: [RFC PATCH] block: add meaningful macro for flush op flags
Date: Sat, 13 May 2023 01:09:11 +0000 [thread overview]
Message-ID: <67376534-ac4a-3cd9-fab6-fd3a062f5e48@nvidia.com> (raw)
In-Reply-To: <20230512130042.GA29078@lst.de>
On 5/12/23 06:00, Christoph Hellwig wrote:
> Hell no. This is just obsfucation. We can look into actually exposing
> REQ_OP_FLUSH at the bio level, but not something like this.
>
and that's why I made it RFC, thanks for the can you please elaborate
on "exposing REQ_OP_FLUSH at the bio level" ?
I'd really like work that ...
-ck
next prev parent reply other threads:[~2023-05-13 1:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 8:07 [RFC PATCH] block: add meaningful macro for flush op flags Chaitanya Kulkarni
2023-05-12 13:00 ` Christoph Hellwig
2023-05-13 1:09 ` Chaitanya Kulkarni [this message]
2023-05-15 1:43 ` Yu Kuai
2023-05-14 11:11 ` Coly Li
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=67376534-ac4a-3cd9-fab6-fd3a062f5e48@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=colyli@suse.de \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sagi@grimberg.me \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
--cc=target-devel@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