LaurieWired Profile picture
Sep 24 4 tweets 2 min read Read on X
Airbags are terrible for hearing.

~170db explosions of air aren't exactly pleasant.

Yet, milliseconds before impact, a clever blast of pink noise can reduce hearing loss 40%!

Mercedes solved it with software 10+ years ago. Still, no one has copied it: Image
Image
If you’re cool, you can activate the stapedius reflex voluntarily. (ear rumblers unite!)

For everyone else, Mercede’s blast of noise manually activates the middle ear muscles.

A taut eardrum taut reduces sound pressure by ~15dB; a LOT on a logarithmic scale. Image
As for why other car manufacturers don’t do this…your guess is as good as mine.

The patents are long expired (~1997). Modern cars *know* when they are about to crash.

Just need some cross-domain messaging to go from the safety-critical logic to the infotainment system. Image
If you want to maintain your sanity, don’t look at the adoption rates of crash safety technologies.

It’s not some major hardware change! We are talking about software here.

I’m sure it’s mostly cheapness; it’d likely take regulation to force other cars to implement said measures.

But there is a *lot* of low hanging fruit if you start looking for it.Image

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with LaurieWired

LaurieWired Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @lauriewired

Sep 25
Encryption is kind of a lie.

Data can be encrypted at rest, and even in transit…but not “in use”.

Fundamentally, CPUs execute arithmetic instructions on decrypted plaintext; even with secure enclaves.

But what if we got *really* clever: Image
Mathematically, there is a solution. It’s just really, really slow.

Fully Homomorphic Encryption allows for arithmetic computation *on* encrypted data.

First published in 2009, each individual (x86) operation took 30 minutes!

AKA, about 10^12 times slower. Image
So why bother?

Ignoring the performance costs, FHE opens up wild possibilities.

Imagine being able to run ML models, Health Data processing, or financial transactions and not having to trust the cloud provider *at all*. Image
Image
Read 4 tweets
Sep 22
SSDs are pretty reliable in a technical sense.

That is, unless you make a really, really bad mistake in firmware.

HP had a line of ~20 different Enterprise SSD models for datacenter use.

In exactly 3 years, 270 days and 8 hours, every one is irrecoverably bricked. Image
Image
If you’re a programmer, you might already guess what happened.

Hint. The bug happens at 32,768 hours of operation time. 2^15.

That’s right, it’s a Signed 16 bit integer overflow. Image
This isn’t a “soft” failure.

The firmware was so borked, that once the overflow occurred, all the data on the drive is gone. Permanently.

Of course, Raid didn’t really help you here either.

Many reports of entire arrays failing within minutes of each other. Image
Read 4 tweets
Sep 16
Everyone knows that the x86 ISA is big.

Modern CPUs have ~1000+ mnemonics. Guess how many make up 90% of compiled C/C++ code?

TWELVE. I'm not kidding.

The question is…what if we shrank it? Image
Image
x86 suffers from what you would call “long tail syndrome”.

A huge amount of legacy instructions used <0.01% of the time.

SHRINK is a cool paper proposing that we *emulate* the old stuff instead.

AKA Instruction Recycling. Image
It’s a radical design, but they trash ~40% of x86 instructions!

Take a ~5% performance hit, slice power consumption in half, and get a nice bump to the critical path.

Trap and Emulate is a fun strategy. Image
Read 4 tweets
Sep 11
How do you program an unknown CPU?

The original specs are gone; no compilers exist, and the ISA is completely unrecognized.

It happens more often than you think, behind very closed doors.

It's almost always military hardware. Image
Image
There is *one* glimpse of this that I know of in the wild.

In 2012, two Russian PhDs researchers gave a presentation at RECon.

Titled quite innocuously, they were tasked with reversing a single, unknown binary.

No hardware. No datasheet. No Documentation. Image
Details about *why* they were doing this are sparse.

No, they aren't reversing Alien CPUs.

If I had to guess, they were likely reversing a Soviet, cold-war era clone of the PDP-11.

Smells like an Avionics / Defense MCU. Image
Image
Read 4 tweets
Sep 3
It’s time to get rid of frame rates.

In weird corners of the internet, researchers and standards committees discuss frameless video containers.

Sensor data as a continuous function, down-sampled to any frame rate you want.

Here's what it'll look like in 10 years: Image
Image
There’s two schools of thought, depending on the crowd you hang around.

NeurIPS folks tend to like continuous-time fields (software).

Hardcore EE types discuss event-based sensing (hardware, timestamps).

Bear with me, it's easier than it sounds: Image
Image
Consumers are gonna see continuous-time fields first.

It doesn’t require new cameras or hardware.

Take a video, re-encode frames into “extracted features”, decode with a ML model, refit to any framerate.

Popular topic at NeurIPS, MPEG Standard is already discussing it. Image
Read 5 tweets
Sep 2
Much like humans, CPUs heal in their sleep.

CPUs are *technically* replaceable / wear items. They don’t last forever.

Yet, the moment stress is removed, transistor degradation (partially) reverses.

It's called Bias Temperature Instability (BTI) recovery: Image
Image
Transistors are little switches.

When you hold a switch on, especially when it’s hot, a bit of charge gets stuck where it shouldn’t.

Every time that happens, it gets a little bit harder to switch.

In other words, the transistor gets a little “lazier”. Image
Over 10 years, in a modern processor, the ALU can slow down 6%!

FPGAs get hit even harder. Run it hard (slightly over-volted), and you’re looking at a few % a year of slowdown.

Not something the average user would notice, but definitely has to be accounted for. Image
Image
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(