Does anyone have a 'good' reason for the chief number to be an a TID for the use of users (nothing to do with kernel internals and implimentation). Removing the chief from the TID allows 32bit TID's with a 'reasonable' number of tasks and threads per task. :)
Cheers Adam
Does anyone have a 'good' reason for the chief number to be an a TID for the use of users (nothing to do with kernel internals and implimentation). Removing the chief from the TID allows 32bit TID's with a 'reasonable' number of tasks and threads per task. :)
Cheers Adam
I'm not yet confirm with the implementation code, but it might have two reasons
1) Theoretically each thread could be chief of each other, so you need full TID In practise I don't think this is a problem because you don't have that much chiefs at all
2) Performance: if the chief number is a TID it is easy to replace the aim of IPCs by that number. If so you may use a fixed offset to reduce the size, let's say chiefs have TIDs FA - FF using FA as offset
Ciao Marcus
l4-hackers@os.inf.tu-dresden.de