Elektrine lite

← Feed

@TomAoki@mastodon.bsd.cafe

Post #2306632

2026-04-26 11:45 UTC

@tfb@mastodon.bsd.cafe @jrsharp@mastodon.sdf.org #FreeBSD had proceeded some parts of "abstraction" in this several decades. For example, separation of buses (like ISA, PCI, USB, ...) and devices connected to any of the buses called "newbus" when it was introduced, GEOM for disks, NETGRAPH for networks. But the appoaches would be different with #NetBSD. Putting newbus (current implementation) aside, others were for "flexibilities" over "abstraction for compatibilities". My understanding in difference between aproaches of FreeBSD and of NetBSD would be... FreeBSD: Make it work and stable, fast for running platform in production first. Then, consider making it portable. NetBSD: Make it elegant and portable by separating machine independent (MI) parts and machine dependent (MD) parts. Then, making it stable would be easier to achieve. So the next would be performance tunings. Link to document about newbus (already not "new" bus but "current" bus, though): https://docs.freebsd.org/en/books/arch-handbook/newbus/

Replies (2)

  • @TomAoki@mastodon.bsd.cafe @tfb@mastodon.bsd.cafe @jrsharp@mastodon.sdf.org Note that some things, such as the busdma framework, we ported from NetBSD. The abstraction layers are moderately similar now (and both inherited the pmap abstraction from 4BSD).

    Open ##2306633

  • @tfb@mastodon.bsd.cafe 2026-04-26 13:52

    @TomAoki@mastodon.bsd.cafe @jrsharp@mastodon.sdf.org Thanks for the link! This looks like FreeBSD (unsurprisingly) chose a good path !

    Open ##2306634