From: Christoph Hellwig <hch@lst.de>
To: Neeraj Singh <nksingh85@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git@vger.kernel.org, "Patrick Steinhardt" <ps@pks.im>,
"Jeff King" <peff@peff.net>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Junio C Hamano" <gitster@pobox.com>,
"Neeraj K. Singh" <neerajsi@microsoft.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Eric Wong" <e@80x24.org>, "Christoph Hellwig" <hch@lst.de>,
"Emily Shaffer" <emilyshaffer@google.com>
Subject: Re: RFC: A configuration design for future-proofing fsync() configuration
Date: Fri, 12 Nov 2021 06:54:21 +0100 [thread overview]
Message-ID: <20211112055421.GA27823@lst.de> (raw)
In-Reply-To: <20211111004724.GA839@neerajsi-x1.localdomain>
On Wed, Nov 10, 2021 at 04:47:24PM -0800, Neeraj Singh wrote:
> It would be nice to loop in some Linux fs developers to find out what can be
> done on current implementations to get the durability without terrible
> performance. From reading the docs and mailing threads it looks like the
> sync_file_range + bulk fsync approach should actually work on the current XFS
> implementation.
If you want more than just my advice linux-fsdevel@vger.kernel.org is
a good place to find a wide range of opinions.
Anyway, I think syncfs is the biggest band for the buck as it will give
you very efficient syncing with very little overhead in git, but it does
have a huge noisy neighbor problem that might make it unattractive
for multi-tenant file systems or git hosting.
next prev parent reply other threads:[~2021-11-12 5:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 15:09 RFC: A configuration design for future-proofing fsync() configuration Ævar Arnfjörð Bjarmason
2021-11-11 0:47 ` Neeraj Singh
2021-11-11 0:57 ` Ævar Arnfjörð Bjarmason
2021-11-17 22:16 ` Neeraj Singh
2021-11-18 19:00 ` Junio C Hamano
2021-11-18 19:46 ` Neeraj Singh
2021-11-12 5:54 ` Christoph Hellwig [this message]
2021-11-17 18:49 ` Neeraj Singh
2021-11-11 18:03 ` Junio C Hamano
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=20211112055421.GA27823@lst.de \
--to=hch@lst.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=e@80x24.org \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=neerajsi@microsoft.com \
--cc=nksingh85@gmail.com \
--cc=peff@peff.net \
--cc=ps@pks.im \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).