HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Saltflow
spdk_blob_top_fs
C2024–2024
Saltflow / spdk_blob_top_fs

spdk_blob_top_fs

A VFS layer on top of SPDK blob layer

2Distinct people
2Mentions
0Explicit recommenders
6GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A VFS layer on top of SPDK blob layer

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 10:50:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2024-05-31 18:20:40 UTC to 2024-05-31 21:23:54 UTC.

012024-05-31 18:00:00 UTC to 2024-05-31 19:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 31, 18:002024-05-31 19:00:00 UTC to 2024-05-31 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 31, 19:002024-05-31 20:00:00 UTC to 2024-05-31 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-05-31 21:00:00 UTC to 2024-05-31 22:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 31, 21:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 31, 18:002024-05-31 18:00:00 UTC2024-05-31 19:00:00 UTC101
May 31, 19:002024-05-31 19:00:00 UTC2024-05-31 20:00:00 UTC000
May 31, 20:002024-05-31 20:00:00 UTC2024-05-31 21:00:00 UTC000
May 31, 21:002024-05-31 21:00:00 UTC2024-05-31 22:00:00 UTC101

What Hacker News says

1 sources
OK, change FUSE to SPDK, you get your userspace VFS layer: https://github.com/Saltflow/spdk_blob_top_fs > Just because you've delegated some small parts into userspace, does not mean that you don't still have a massive monolithic kernel with metric tons of infrastructure and subsystems all running in the same kernel address space, oftentimes not even as dedicated threads. That's up to you to keep around. No need to compile in subsystems and drivers you don't need. HID is pushed userspace by HID-BPF and it works great. USB, I2C, SPI can all be handled by direct messages to the device. These objections are pedantry around what exactly is micro about a microkernel. UIO lets you drive any hardware via userspace memory maps, it's just usually easier to slap it into a pre-built kernel subsystem more than any need for code to be in kernel mode.
Read the rest
> A monolithic [sic] kernel is a tiny kernel that does not do much more than message passing. Linux is very far away from that, your "userspace servers" for FUSE and similar things are better called "delegates" for subsystems that still reside in the kernel itself. Your message passing is my delegation through, say, netlink. Perhaps you are describing an exokernel concept where only the barest minimum is run in kernel mode? Mach runs a lot more in kernel mode than necessary, even L4 isn't a "true" microkernel if you are ultra-pedantic and run on processors with, say, userspace interrupts.
In Ask HN: Why are all major operating systems monolithic?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.