From: Damien Le Moal <dlemoal@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Subject: Re: [PATCH 2/4] loop: set LO_FLAGS_DIRECT_IO in loop_assign_backing_file
Date: Tue, 4 Feb 2025 09:55:51 +0900 [thread overview]
Message-ID: <d0d899ba-3014-4977-b107-c16168b3fa54@kernel.org> (raw)
In-Reply-To: <20250131120120.1315125-3-hch@lst.de>
On 1/31/25 21:00, Christoph Hellwig wrote:
> Assigning LO_FLAGS_DIRECT_IO from the O_DIRECT flag is related to
> assigning a new backing file. Move the assignment in preparation
> of using the flag more and earlier.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2025-02-04 0:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 12:00 loop: take the file system minimum dio alignment into account v2 Christoph Hellwig
2025-01-31 12:00 ` [PATCH 1/4] loop: factor out a loop_assign_backing_file helper Christoph Hellwig
2025-02-04 0:55 ` Damien Le Moal
2025-01-31 12:00 ` [PATCH 2/4] loop: set LO_FLAGS_DIRECT_IO in loop_assign_backing_file Christoph Hellwig
2025-02-04 0:55 ` Damien Le Moal [this message]
2025-01-31 12:00 ` [PATCH 3/4] loop: check in LO_FLAGS_DIRECT_IO in loop_default_blocksize Christoph Hellwig
2025-02-04 0:56 ` Damien Le Moal
2025-01-31 12:00 ` [PATCH 4/4] loop: take the file system minimum dio alignment into account Christoph Hellwig
2025-02-04 1:01 ` Damien Le Moal
2025-02-24 23:01 ` loop: take the file system minimum dio alignment into account v2 Christoph Hellwig
2025-02-24 23:18 ` Jens Axboe
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=d0d899ba-3014-4977-b107-c16168b3fa54@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@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 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.