Re: Include DaynaPort by default in GENERIC?

[Dennis Clarke <dclarke%blastwave.org@localhost>]

On 3/24/26 12:42, Erik LaBine wrote:
> On March 24, 2026 12:06:30 PM EDT, Dennis Clarke <dclarke%blastwave.org@localhost> wrote:
> >     Has anyone tried to bond interfaces together? I figure with LACP
> > bonding of all four qeX interfaces the thing would be just fine over the
> > NFS with *almost* reseonable performance.
>
> Admittedly I haven't tried bonding interfaces, but I do suspect you're likely running into SBus limits or possibly even MBus limits there rather than anything about the NIC itself. The quad ethernet should be able to do 100 Mb/s, no? I believe the theoretical max throughout isn't too far off from that.
>
> Anecdotally, I've never seen better than 760kB/s (~6Mb/s) on an SS5 with a 170MHz TurboSparc. But that was with an SSL connection and the usual HTTP overhead. And on a sketchy gigabit fibre driver I hand rolled.
>
> Erik

deimos#
deimos# uname -a
NetBSD deimos 10.1 NetBSD 10.1 (GENERIC.MP) #0: Mon Dec 16 13:08:11 UTC 
2024 
mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/sparc/compile/GENERIC.MP sparc
deimos# sysctl hw.model
hw.model = SUNW,SPARCstation-20 (Ross,RT626 @ 200 MHz, on-chip FPU)
deimos# sysctl hw.ncpu
hw.ncpu = 2
deimos# sysctl hw.physmem
hw.physmem = 536334336
deimos#

deimos# ifconfig -a
le0: flags=0x8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        ec_capabilities=0x1<VLAN_MTU>
        ec_enabled=0
        address: 08:00:20:00:de:ad
        media: Ethernet autoselect
qe0: flags=0x8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        address: 08:00:20:00:de:ad
        media: Ethernet autoselect (10base5)
        status: active
qe1: flags=0x8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        address: 08:00:20:00:de:ad
        media: Ethernet autoselect (10base5)
        status: active
qe2: flags=0x8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        address: 08:00:20:00:de:ad
        media: Ethernet autoselect (10base5)
        status: active
qe3: flags=0x8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        address: 08:00:20:00:de:ad
        media: Ethernet autoselect (10base5)
        status: active
hme0: flags=0x8002<BROADCAST,MULTICAST> mtu 1500
 
capabilities=0x3c00<TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
        enabled=0
        ec_capabilities=0x1<VLAN_MTU>
        ec_enabled=0
        address: 08:00:20:00:de:ad
        media: Ethernet autoselect (100baseTX half-duplex)
        status: active
be0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ec_capabilities=0x1<VLAN_MTU>
        ec_enabled=0
        address: 08:00:20:00:de:ad
        media: Ethernet autoselect (100baseTX half-duplex)
        status: active
        inet6 fe80::a00:20ff:fe00:dead%be0/64 flags 0 scopeid 0x7
        inet 172.16.35.16/26 broadcast 172.16.35.63 flags 0
lo0: flags=0x8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33176
        status: active
        inet6 ::1/128 flags 0x20<NODAD>
        inet6 fe80::1%lo0/64 flags 0 scopeid 0x8
        inet 127.0.0.1/8 flags 0
deimos#

Why are all the interfaces stuck to the same MAC address? Could that
be due to the local-mac-address value in the PROM ?

Oh, also, this is boot and run *entirely* over the network. Diskless.

--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken