On Sun, Apr 21, 2019 at 8:42 PM Daniel Cegiełka <daniel.cegie...@gmail.com> wrote: > allocate to ext4+RAID (md) a large block of memory (fallocate). Then > use this block of memory as a huge ring buffer and they simply copy > memory using mmap. Of course, data integrity is checked at every step: > > https://fmad.io/blog-10g-capture-data-integrity.html > > So they don't use directly any popular filesystem. They moved > everything to the user's space. Next, I will give another example of > moving certain functionalities to the user's space.
I just want to add a similar preferred use-case of mine: LMDB (or any other embedded database or key-value store) which allows me to implement a very fast (as in orders of magnitude) file-system like store, suitable especially for small "files", but many in number. And indeed in this scenario the file-system dissapeares into the background, as all the integrity (especially atomicity) and performance is mainly provided by the embedded database itself. However on the flipside you loose the nice ability to use `mc` (or your favourite file browser) to peek into the "store"... Let alone standard UNIX tools like `cp` or `mv`... However, as 9p was mentioned in this thread one could implement a server to allow mounting it. Ciprian.
