News for hackers. Stuff that matters.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by Spivak on Friday May 03, 2019 @12:48PM (#19820014)
What would you replace it with? At the very core you need two things: the notion of a unit of data and some metadata to address it. To be as flexible as possible that unit of data would probably modeled as a sequence of individually addressable bytes but it could be more structured. Such a thing is dangerous because if your structure isn't sufficiently expressive 20 years down the road people will end up imposing their own structure on top of obj.binary and there goes all the work.

Once you have data and handles to access it you might start wanting some convenience features like access control, locking, namespacing, constraints, relationships.

I don't disagree that we can drop many of the current filesystem semantics but fundamentally all that really means is changing is the query language to access objects and manipulate their metadata.

I also don't disagree about process hierarchy. Being able to express relationships between processes beyond parent-child natively without farming out to an external scheduler would be awesome.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by stcredzero on Friday May 03, 2019 @01:09PM (#19820192)
What would you replace it with? At the very core you need two things: the notion of a unit of data and some metadata to address it

There were some experiments along these lines. Instead of files, just make everything an object and have orthogonal persistence for every object. In a way, this was what the early Smalltalk implementations were working towards.

I don't disagree that we can drop many of the current filesystem semantics but fundamentally all that really means is changing is the query language to access objects and manipulate their metadata.

One thing which Smalltalk demonstrates, is that the query language can simply be the same language used to implement the OS. Activity which looks a lot like database querying, but for objects, not database rows was just an expert level debugging trick of Smalltalk programmers.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by scroot on Friday May 03, 2019 @12:57PM (#19820089)
Object systems
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by silversconfused on Friday May 03, 2019 @01:49PM (#19820591)
Ok, but what does the level below that look like?
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by scroot on Friday May 03, 2019 @02:20PM (#19820893)
I'm not sure there has to be a lower level at all, aside from asm and machine language
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by Spivak on Friday May 03, 2019 @02:49PM (#19821166)
Okay so you have a device driver that exposes your underlying hard disk as a single contiguous segment of blocks of a given size. You have objects which are blobs of heterogeneously sized arbitrary data with an addressing scheme.

The software that marries these two things is basically a filesystem driver (in that you can implement filesystem semantics on top of it -- hell Ceph does it right now).

Nothing about a modern Linux/BSD system really stands in the way of doing this.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by scroot on Friday May 03, 2019 @03:21PM (#19821417)
Of course, you need some agent that can communicate with the hard disk and that knows how to manage memory. Maybe its one driver, maybe its several, but these can also just be objects. Live objects, I mean. Not just blobs of data, but actors that have behaviors and are always "running." You don't even need the concept of files or filesystems. And if you do, better left to a higher level
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by laughinghan on Friday May 03, 2019 @05:02PM (#19822247)
Isn't the whole point of persistent storage like hard drives to deal with the fact that computers shut off sometimes, and nothing can be "always 'running'"?

Something below the object level (possibly part of the object system, possibly a layer below that) needs to read from disk and bootstrap all those agents/live objects/actors into existence.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by fragmede on Friday May 03, 2019 @08:48PM (#19823526)
The storage on disk doesn't have to be a traditional hierarchical filesyste,m for anything after the kernel is loaded (+drivers), as long as the kernel is able to recombobulate the agents off the block addressable storage device, it can store them however it wants. Simply serializing swaths of memory to/from disk may not be the most efficient, but that should show its possible.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by scroot on Friday May 03, 2019 @05:27PM (#19822449)
Well of course they aren't running when the computer is off. And yeah, you'd need something to bootstrap the system the same way you need a bootloader