nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqqv5atqz9k9c54q8c28kra6sfata0wk7w7x5gkrnde8vmxe5gt00q8mmv7s (nprofile…mv7s)
Having written firmware for switches at multiple vendors, I'm guessing that at config time they've only allocated one set of data structures for each QSFP+ that isn't doing breakout, and so adding a breakout makes them want to change the allocation. They should just always allocate four for QSFP+, QSFP28, QSFP56, etc.
Switch firmware wants to do as little dynamic allocation as possible, ideally none, to prevent memory fragmentation problems later.
🇺🇦 haxadecimal 🚫👑
npub1nl…kxk0p
2026-05-28 05:03:15 UTC
in reply to nevent1q…zg45
Author Public Key
npub1nlrs0z6s56nm5y8e73nx38f59e37ym3sjcw9r8v2hlehetp6fqxqdkxk0pSeen on
wss://relay.ditto.pubPublished at
2026-05-28 05:03:15 UTCEvent JSON
{
"id": "2d33609cd3602ba9e8dcfb60995bc9d4d7b686de513c79b177f5651a1c38f778",
"pubkey": "9fc7078b50a6a7ba10f9f466689d342e63e26e30961c519d8abff37cac3a480c",
"created_at": 1779944595,
"kind": 1,
"tags": [
[
"p",
"0329d58045b1714a80f851ec3eea09eafaf75bcef1a88b0e6dc9d9b366885bde",
"wss://relay.ditto.pub"
],
[
"p",
"c35a8fae05a838b863707803bb1fdfcfcbb39adcf01ee1a9fc52ef44998ce4c0",
"wss://relay.ditto.pub"
],
[
"e",
"7fa4a64dbba6b9b3d18ec376bcb07720d5dbe4b1b2c7110d1b401d64e5ee2bff",
"wss://relay.ditto.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/brouhaha/statuses/116650449003110365",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqqv5atqz9k9c54q8c28kra6sfata0wk7w7x5gkrnde8vmxe5gt00q8mmv7s \nHaving written firmware for switches at multiple vendors, I'm guessing that at config time they've only allocated one set of data structures for each QSFP+ that isn't doing breakout, and so adding a breakout makes them want to change the allocation. They should just always allocate four for QSFP+, QSFP28, QSFP56, etc.\nSwitch firmware wants to do as little dynamic allocation as possible, ideally none, to prevent memory fragmentation problems later.",
"sig": "ea44257a98c09ae015ad997dcbd0702288652780f9b80b4deb85deea50caf432cf241d4e8960e0f7e92f689c13604753f4e7feb66159be17ba64dda2224bc2dc"
}