Read the defrag code in other well-established fs like ext4 or btrfs. They all have limitations(or caveats, if you will). It's one of those problems where you just have to throw money at it and hope for the best. Even Microsoft kinda just gave up on it because it's really a pointless exercise at this point in time and age.
I did the same. Was genuinely curious. Didn't get much from it. I'm still confused.
The code base is huge for an LLM to handle, perhaps it was generated over multiple prompts idk. Not sure if someone can train a model on the kernel code or exfatprogs and generate the code. I doubt someone with such expertise would even go through the process when they can just write the code themselves which is much easier.
Multiple prompts are mandatory for anything non-trivial or/and larger in scope. That said, the exfatprogs repo is ~60k tokens (in 8k LOC) and Linux's exfat driver* is ~40k tokens (in 6k LOC). So directly relevant code is ~100k tokens (in 14k LOC). Not that extensive.
>Not sure if someone can train a model on the kernel code or exfatprogs and generate the code.
They can certainly finetune such a model. Not a crazy idea, just computationally expensive. (But less expensive than training from scratch.)
*Of course Linux driver also uses many includes so if consider those alongside linked code the number goes significantly up.