It would be a little bit weird and amazing to have Carl Sassenrath contribute to AROS
He's unlikely to have thought about exec in nearly 30 years. If he has any sense he's forgotten everything he knew about it.
There is unlikely to be any major design work left right now, although there might be some minor design work depending on what is found during coding/testing.
Coding, testing and fixing the current design and then testing the speed to see whether any changes are required is the current goal.
Even if it wastes 10% of each core then SMP could still have a big win.
However moving data between cpu cores might have an overhead, so sharing tasks across cpu's might not be the best strategy. It might make more sense to saturate a cpu and only spin up another cpu if there are still more tasks ready.
Only when the simple implementation is done can you get enough information to make those decisions. It's complex enough that guessing isn't easy.
I merely asked matthey to clarify his "You have already proved some people wrong with your experiments" statement.
Some people said you couldn't do SMP with exec. Technically he hasn't proved them wrong as he's moved fields out of execbase, which was the only reason you can't do SMP with exec. His plan is to avoid the theoretical discussions of the implications of that and just try to code it, often this is the only way to solve an argument & it's actually how AROS came to exist.
Once you have an implementation then have a baseline. After evaluating it for any drawbacks you can try to address those and then when you test it you can know whether it's better or worse. The problem with arguing over technical concepts is that it is very difficult to judge their merit. Until you see the code running it's unlikely you'll have any idea what the cache implications are of using SMP etc.