Mark :verified: on Nostr: npub1rtqnl…crx2j Well, I'm not sure I could describe another way to handle the ...
npub1rtqnlxla0y36cmqs548ry0ecrah0y5vd5dds0sk80y6jeluwrdasqcrx2j (npub1rtq…rx2j)
Well, I'm not sure I could describe another way to handle the volume of updates they need to process.
We only managed a dozen (or so) patches - most were small but some like BIGPHYSMEM were essential for one hardware interface and was quite large. It was HARD to allocate large contiguous chunks of physical memory without it. Not sure they ever fixed that.
Well, I'm not sure I could describe another way to handle the volume of updates they need to process.
We only managed a dozen (or so) patches - most were small but some like BIGPHYSMEM were essential for one hardware interface and was quite large. It was HARD to allocate large contiguous chunks of physical memory without it. Not sure they ever fixed that.