It's not about the number of cores, it's about the expense of the context switches when servicing the interrupt. The x86 architecture doesn't have register banks the way the old Sparc chips did. Every context switch the registers have to be dumped to ram and the new contents loaded from ram. That's an expensive operation.

If you start a mile north of the South Pole, walk a mile south, then you cannot walk west, so it still fails.

Also, the North Pole isn't ice-free all year long. (I've not been keeping up with how much (if it has happened yet) it is ice-free during a year, but it's certainly not the whole year. Yet.)

You are in a square room. All four sides have Southern exposure. A bear walks by. What color is it? :)

You can't walk South from the South Pole. :)

uBlock isn't available for the _Android_ version, which is the problem. I use it on the desktop; I'd love to use it on Android as well.

Perhaps what I should say is: that's not a brain teaser, it's basic competence in geospatial systems wrapped up in a tidy bow.

That's not much of a brain teaser.

Yep, a few years ago I used to send a LOT of CDR's and DVDR's to friends in Canada I would trade for Cuban Cigars.

I say we take the Politicians money first. That would be the ultimate in honest.

Or, simply configure the pumps to have different IP addresses. Does his boss pour gasoline on him and set him on fire if he changes their IP addresses?

Which is why it should be tied to the car value.

Driving a Bugatti Veyron? you pay $22.50 per mile for the tax.
Driving a 1995 Civic? $0.05 per mile.

Very simple to do, which means the government will completely fuck it up.

Get a switch which supports VLANs, 1 vlan on each port and the trunk on your laptop. Then run the mfg's software inside virtual machines, each of which has one of the vlans connected to its virtual ethernet, using the mfg's IP address. Now you can run all the updates in parallel.

The better solution is for the mfg to give you software and a configuration that does not suck. But if you're stuck with it, the above will work just fine.

Not really. The x86 architecture can't handle the interrupts. That's why modern cards don't interrupt on every packet received.

"Shipping costs would also be prohibitive."

no it's not. jam them in as tight as possible into a $5.95 flat rate box.

They mostly don't forward until the entire packet is received. That can't work unless the sending interface is the same or lower speed and the hardware for it (hardware fast path at high data rates) tends to be brittle.

Linux does not do this. The ethernet cards Linux uses do not do this. They work with complete packets. In the case of OSes on PC architectures, the kernel may not even get an interrupt until the card has multiple packets to deliver.