Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
1–10 of 45 posts
Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#2Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#3Unfortunately the metadata (list of files) is stored in memory, not network. Not quite as unreliable as I would like.
Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#4Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#5Only looked at the read path, which is roughly:
* filesystem receives read
* blocks on a semaphore (https://github.com/yarrick/pingfs/blob/master/chunk.c#L141)
* network thread wakes up semaphore when ICMP reply containing data is received
* filesystem thread copies data into new buffer to return from syscall
* filesystem relinquishes chunk back to network thread, which wakes up, sends it back to be echoed on the network via ICMP, and frees the in-memory buffer (https://github.com/yarrick/pingfs/blob/master/chunk.c#L107)
How silly :)
Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#6Goodbye then.
Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#7Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#8This is exactly what I needed - not a lot of people are doing eventually inconsistent databases yet. If theres a network partition, shits probably fucked anyways so its best to throw away all your data. Unfortunately the metadata (list of files) is stored in memory, not network. Not quite as unreliable as I would like.
Note: joke assumes parent poster was somewhat humorous