qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pinku Deb Nath <prantoran@gmail.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v6] block/file-posix.c: Use pwritev2() with RWF_DSYNC for FUA
Date: Tue, 8 Apr 2025 12:03:02 -0700	[thread overview]
Message-ID: <CABqzzD6JWKpnR6Prwvna_ScYSXg3UNTLooXLZ2+nYpPO6c6VnA@mail.gmail.com> (raw)
In-Reply-To: <20250408154338.GD550845@fedora>

[-- Attachment #1: Type: text/plain, Size: 1997 bytes --]

Yay! 😊

On Tue, Apr 8, 2025, 8:43 a.m. Stefan Hajnoczi <stefanha@redhat.com> wrote:

> On Mon, Apr 07, 2025 at 08:47:30AM -0700, Pinku Deb Nath wrote:
> > Full Unit Access (FUA) is an optimization where a disk write with the
> > flag set will be persisted to disk immediately instead of potentially
> > remaining in the disk's write cache.
> >
> > This commit address the todo task
> > for using pwritev2() with RWF_DSYNC in the thread pool section of
> > raw_co_prw(), if pwritev2() with RWF_DSYNC is available in the host,
> > which is always the case for Linux kernel >= 4.7.
> >
> > The intent for FUA is indicated with the BDRV_REQ_FUA flag.
> > The old code paths are preserved in case BDRV_REQ_FUA is off
> > or pwritev2() with RWF_DSYNC is not available.
> >
> > Support for disk writes with FUA is handled in qemu_pwritev_fua(),
> > which uses pwritev2() with RWF_DSYNC if available, otherwise falls
> > back to pwritev2() with no flags followed by flush using
> > handle_aiocb_flush().
> >
> > If pwritev2() is not implemented, then disk write in the linear FUA
> > will fallback to pwrite() + handle_aiocb_flush().
> >
> > Signed-off-by: Pinku Deb Nath <prantoran@gmail.com>
> >
> > ---
> >
> > v5:
> > - Use pwritev for unsupported OSes
> >
> > v4:
> > - Add fallback when qemu_pwritev_fua() returns ENOSYS
> > - Similar fallback was not added for handle_aiocb_rw_vector()
> > since there is a preadv_present check in handle_aiocb_rw()
> >
> > v3:
> > - Changed signature to add fd, iov, nr_iov
> > - Return -ENOSYS for non-Linux hosts
> >
> > v2:
> > - Moved handle_aiocb_flush() into qemu_pwritev_fua()
> > - In handle_aiocb_rw_linear(), iovec with iovcnt=1 is created
> > based on the assumption that there will be only one buffer
> > ---
> >  block/file-posix.c | 68 ++++++++++++++++++++++++++++++++++++++--------
> >  1 file changed, 56 insertions(+), 12 deletions(-)
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
>

[-- Attachment #2: Type: text/html, Size: 2676 bytes --]

  reply	other threads:[~2025-04-08 19:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 15:47 [PATCH v6] block/file-posix.c: Use pwritev2() with RWF_DSYNC for FUA Pinku Deb Nath
2025-04-08 15:43 ` Stefan Hajnoczi
2025-04-08 19:03   ` Pinku Deb Nath [this message]
2025-04-09  7:48 ` Kevin Wolf
2025-04-11 16:17 ` Eric Blake

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=CABqzzD6JWKpnR6Prwvna_ScYSXg3UNTLooXLZ2+nYpPO6c6VnA@mail.gmail.com \
    --to=prantoran@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).