public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Neutron Sharc <neutronsharc@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Fwd: does xfs support aio_fsync?
Date: Fri, 28 Oct 2022 15:58:04 -0700	[thread overview]
Message-ID: <Y1xefLbvx96dNUqq@magnolia> (raw)
In-Reply-To: <CAB-bdyTJjM7ju-ku6w1Tib06r70FbZ8r0y8mfBaKu4XQDuMeUw@mail.gmail.com>

On Fri, Oct 28, 2022 at 03:11:15PM -0700, Neutron Sharc wrote:
> Hello all,
> I have a workload that benefits the most if I can issue async fsync
> after many async writes are completed. I was under the impression that
> xfs/ext4 both support async fsync so I can use libaio to submit fsync.
> When I tested with io_submit(fsync),  it always returned EINVAL.  So I
> browsed the linux source (both kernel 3.10,  4.14)  and I found
> xfs/xfs_file.c doesn't implement "aio_fsync", nor does ext4/file.c.
> 
> I found an old post which said aio_fsync was already included in xfs
> (https://www.spinics.net/lists/xfs/msg28408.html)
> 
> What xfs or kernel version should I use to get aio_fsync working?  Thanks all.

$ git blame -L 1606,+2 fs/aio.c
a3c0d439e4d92 (Christoph Hellwig 2018-03-27 19:18:57 +0200 1606) static void aio_fsync_work(struct work_struct *work)
a3c0d439e4d92 (Christoph Hellwig 2018-03-27 19:18:57 +0200 1607) {

...some time around the 4.19 LTS?

--D

> 
> 
> Shawn

  reply	other threads:[~2022-10-28 22:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAB-bdyRWCJLDde4izM_H-Bh9wPg-Enas+D4VvTROWEpVy0ZgZg@mail.gmail.com>
2022-10-28 22:11 ` Fwd: does xfs support aio_fsync? Neutron Sharc
2022-10-28 22:58   ` Darrick J. Wong [this message]
2022-10-29 21:01   ` Dave Chinner
2022-10-30 16:44     ` Shawn

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=Y1xefLbvx96dNUqq@magnolia \
    --to=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=neutronsharc@gmail.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