git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: RFC: A configuration design for future-proofing fsync() configuration

From
CHChristoph Hellwig <hch@lst.de>
Date
Nov 12, 2021, 05:54 UTC
Message-ID
<20211112055421.GA27823@lst.de>
In-Reply-To
<20211111004724.GA839@neerajsi-x1.localdomain>
On Wed, Nov 10, 2021 at 04:47:24PM -0800, Neeraj Singh wrote:
Show 5 quoted lines
> 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.

Previous: Neeraj SinghNext: Neeraj Singh
Message 7 of 9 in “RFC: A configuration design for future-proofing fsync() configuration”
  1. Ævar Arnfjörð BjarmasonNov 10, 2021
  2. Neeraj SinghNov 11, 2021
  3. Ævar Arnfjörð BjarmasonNov 11, 2021
  4. Neeraj SinghNov 17, 2021
  5. Junio C HamanoNov 18, 2021
  6. Neeraj SinghNov 18, 2021
  7. Christoph HellwigNov 12, 2021
  8. Neeraj SinghNov 17, 2021
  9. Junio C HamanoNov 11, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.