From: RIc Wheeler <ricwheeler@gmail.com>
To: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org
Cc: Zach Brown <zab@zabbo.net>
Subject: [LSF/MM/BPF TOPIC] Design challenges for a new file system that needs to support multiple billions of file
Date: Sun, 2 Feb 2025 22:39:57 +0100 [thread overview]
Message-ID: <048dc2db-3d1f-4ada-ac4b-b54bf7080275@gmail.com> (raw)
I have always been super interested in how much we can push the
scalability limits of file systems and for the workloads we need to
support, we need to scale up to supporting absolutely ridiculously large
numbers of files (a few billion files doesn't meet the need of the
largest customers we support).
Zach Brown is leading a new project on ngnfs (FOSDEM talk this year gave
a good background on this -
https://www.fosdem.org/2025/schedule/speaker/zach_brown/). We are
looking at taking advantage of modern low latency NVME devices and
today's networks to implement a distributed file system that provides
better concurrency that high object counts need and still have the
bandwidth needed to support the backend archival systems we feed.
ngnfs as a topic would go into the coherence design (and code) that
underpins the increased concurrency it aims to deliver.
Clear that the project is in early days compared to most of the proposed
content, but it can be useful to spend some of the time on new ideas.
next reply other threads:[~2025-02-02 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 21:39 RIc Wheeler [this message]
2025-02-03 15:22 ` [LSF/MM/BPF TOPIC] Design challenges for a new file system that needs to support multiple billions of file Amir Goldstein
2025-02-03 16:18 ` Ric Wheeler
2025-02-04 1:47 ` Dave Chinner
2025-02-05 8:05 ` Ric Wheeler
2025-02-06 18:58 ` Zach Brown
2025-02-06 23:36 ` Andreas Dilger
2025-02-03 15:23 ` Ric Wheeler
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=048dc2db-3d1f-4ada-ac4b-b54bf7080275@gmail.com \
--to=ricwheeler@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=zab@zabbo.net \
/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).