From: Kanchan Joshi <joshi.k@samsung.com>
To: Christoph Hellwig <hch@lst.de>, Anuj Gupta <anuj1072538@gmail.com>
Cc: asml.silence@gmail.com, djwong@kernel.org, cem@kernel.org,
brauner@kernel.org, axboe@kernel.dk, linux-block@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
anuj20.g@samsung.com, nj.shetty@samsung.com
Subject: Re: [RFC 4/4] xfs: support dma-buf registered buffers for direct I/O
Date: Sat, 17 Oct 2026 23:49:58 +0530 [thread overview]
Message-ID: <bce9928f-8370-4dad-a269-5fdb2c5315b6@samsung.com> (raw)
In-Reply-To: <20261016092855.GD23141@lst.de>
On 10/16/2026 2:58 PM, Christoph Hellwig wrote:
>> +/*
>> + * A realtime file's data lives on the realtime device, anything else on the
>> + * data device. If a file is switched between them after registration, the
>> + * block layer cross-device check refuses the I/O.
>> + */
>> +static int
>> +xfs_file_init_dma_buf_io_ctx(
>> + struct file *file,
>> + struct dma_buf_io_ctx *ctx)
>> +{
>> + struct xfs_inode *ip = XFS_I(file_inode(file));
>> +
>> + return iomap_file_init_dma_buf_io_ctx(file,
>> + xfs_inode_buftarg(ip)->bt_bdev, ctx);
>> +}
> Ah, this is where the previous cross check comes from. What about
> simply disallowing toggling the RT flag with outstanding reservations
> instead?
So, instead of patch 2, this is about setting a new in-core inode flag
here iff the registration was successful. And checking this new flag to
refuse toggling RT?
next prev parent reply other threads:[~2026-10-17 18:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 9:19 [RFC 0/4] fs: support dma-buf backed direct I/O Anuj Gupta
2026-10-16 9:19 ` [RFC 1/4] block: factor out bdev_init_dma_buf_io_ctx() Anuj Gupta
2026-10-16 9:23 ` Christoph Hellwig
2026-10-16 9:19 ` [RFC 2/4] block: refuse a dma-buf bio for a disk the buffer was not registered on Anuj Gupta
2026-10-16 9:24 ` Christoph Hellwig
2026-10-21 15:12 ` Pavel Begunkov
2026-10-16 9:19 ` [RFC 3/4] iomap: add dma-buf direct I/O guards and registration helper Anuj Gupta
2026-10-16 9:26 ` Christoph Hellwig
2026-10-16 9:19 ` [RFC 4/4] xfs: support dma-buf registered buffers for direct I/O Anuj Gupta
2026-10-16 9:28 ` Christoph Hellwig
2026-10-17 18:19 ` Kanchan Joshi [this message]
2026-10-18 22:28 ` Pavel Begunkov
2026-10-19 10:29 ` Anuj gupta
2026-10-17 22:54 ` [RFC 0/4] fs: support dma-buf backed " shinichiro.kawasaki
2026-10-18 13:32 ` Shin'ichiro Kawasaki
2026-10-18 22:18 ` Pavel Begunkov
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=bce9928f-8370-4dad-a269-5fdb2c5315b6@samsung.com \
--to=joshi.k@samsung.com \
--cc=anuj1072538@gmail.com \
--cc=anuj20.g@samsung.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nj.shetty@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox