Remote
Linux kernel IO dabbler @ Meta
0
Followers
0
Following
19
Posts
Joined November 08, 2022
Posts
Replying to
@brauner@mastodon.social
@brauner@mastodon.social @ljs@mastodonapp.uk It's just gym selfies and pics of cats. At least that's what @vbabka@mastodon.social tells me, he's been reviewing them.
Open post
Replying to
@AndresFreundTec@mastodon.social
@AndresFreundTec@mastodon.social @bert_hubert@eupolicy.social I'm almost hoping this is targeted and they find out they messed with exactly the wrong guy with this stunt ;-)
0
1
0
0
Open post
Replying to
@bert_hubert@eupolicy.social
@bert_hubert@eupolicy.social @AndresFreundTec@mastodon.social Was thinking the same... The caller said 'google' here and I figured that was a scam, so I didn't pick up. But the voicemail they left sounds eerily similar to yours. This was at 1:05PM MT time.
Edit: and the number they called from was shown as 650-203-0000.
1
1
0
0
Open post
Replying to
@AndresFreundTec@mastodon.social
@AndresFreundTec@mastodon.social got the same one here…
2
1
0
0
Open post
Replying to
@Aissen@social.treehouse.systems
@Aissen@social.treehouse.systems @hyeyoo@social.kernel.org @ljs@mastodonapp.uk @vbabka@mastodon.social @gregkh@social.kernel.org This is the way. Nothing is free, have the people that want to use it pay the cost. The kernel people have enough to do without maintaining hardware they don't even have.
1
0
0
0
Open post
Replying to
@Aissen@social.treehouse.systems
@Aissen@social.treehouse.systems @hyeyoo@social.kernel.org @ljs@mastodonapp.uk @vbabka@mastodon.social @gregkh@social.kernel.org The retro argument is quite typical. Someone should setup a retro tree and maintain it, those drivers and nommu (and 486 support!) can live there. There's zero reason to keep purely retro support in the kernel imho - if it hasn't been sold in products in decades, it need not be in the mainline tree.
2
3
0
0
Open post
Replying to
@axboe@fosstodon.org
@Aissen@social.treehouse.systems @gregkh@social.kernel.org @ljs@mastodonapp.uk @vbabka@mastodon.social And let me just add, if you're not able or willing to do any work on this, your opinion on whether or not some code should be removed or stay in the kernel is worth absolutely nothing. Just stay silent, accept the decision of those that ARE carrying this maintenance burden.
8
1
1
0
Open post
Replying to
@hyeyoo@social.kernel.org
@hyeyoo@social.kernel.org @ljs@mastodonapp.uk @vbabka@mastodon.social @gregkh@social.kernel.org @Aissen@social.treehouse.systems "Look I found a bug, how great am I"
2
6
0
0
Open post
Replying to
@hyeyoo@social.kernel.org
@hyeyoo@social.kernel.org @ljs@mastodonapp.uk @vbabka@mastodon.social @gregkh@social.kernel.org @Aissen@social.treehouse.systems That's not bittersweet, that's just laziness. So much easier to run LLMs on code and report issues they often don't even understand, than it is to write a patch.These people don't care about the code, that's not why they are reporting the issues.
2
8
0
0
Open post
Replying to
@Aissen@social.treehouse.systems
@Aissen@social.treehouse.systems @gregkh@social.kernel.org @ljs@mastodonapp.uk @vbabka@mastodon.social Ah had not even seen that. It's not bitter sweet, removing code is a Good Thing, and now there's finally a reason to do it that carries some weight. Before this ordeal, it was always punted with "ah well the maintenance burden isn't THAT big". Kill it with fire, git history is forever and if someone steps up to properly maintain a piece of code, it can be brought back.
We're not running a museum.
22
2
5
0
Open post
Replying to
@Aissen@social.treehouse.systems
@Aissen@social.treehouse.systems @gregkh@social.kernel.org @ljs@mastodonapp.uk @vbabka@mastodon.social As any sane person should! Honestly, I'm hope this will be the silver lining to the slew of mostly garbage LLM bug reports - yank the old and untested code from the kernel, not just nommu.
3
22
0
0
Open post
Replying to
@axboe@fosstodon.org
@gregkh@social.kernel.org Actually I can buy my own, what I'd really like is for us to kill nommu. It has zero reason to exist, and it's largely untested garbage.
Forget the booze, that's what I want.
7
24
3
0
Open post
Replying to
@gregkh@social.kernel.org
@gregkh@social.kernel.org I'll take a whisky over a box of chocolates anyway ;-)
2
1
0
0
Open post
Replying to
@josefbacik@hachyderm.io
@josefbacik@hachyderm.io We just have to sort out the stupidities further down. Like Andres says too. And as you know there really are zero reasons why that can't be done, your work is actually a great first step! Heading OOO for a week, I'll take a stab at some of this when I'm back.
0
0
0
0
Open post
Replying to
@axboe@fosstodon.org
This took a while. One funny side quest was claude deciding it should check if my (destructive) reproducer was also slow on virtio-blk, then proceeding to blow away /dev/vda and concluded that yeah virtio-blk was fine. When confronted with this, it just said "Yes, I did do that".
I then asked it to fix up vda, as it blew away the first 128MB of it. And it did.
8
0
0
0
Open post
Had some quality time with claude debugging a slowness with AHCI/scsi and aio=io_uring. See below link for details (patch 1 is where it's at), but tldr is up to 60-80x improvement in performance for the case that hits ppoll idle all the time.
https://lore.kernel.org/qemu-devel/20260213143225.161043-1-axboe@kernel.dk/
0
1
2
0
Open post
Replying to
@torsteinv@mastodon.social
@torsteinv @JPZ @sven It's just the typical baseless speculation by a non-expert, which is by definition useless and just noise.
You're either trolling, or just ignorant. Congrats, first block for me on fedi 🙂
5
0
0
0
Open post
Replying to
@torsteinv@mastodon.social
@torsteinv @sven Oh no, Torstein has "called it", guess that's it for the project...
5
0
0
0
Remote instance
fosstodon.org
Open on original server