Yes, that is true, but task_struct's size hasn't changed significantly since 2.4. Since 2.4 doesn't have a stack space problem, I figured there must have been something that changed in 2.5 which motivated the developers to optimize for stack space.
Its all about improvment. There WAS a space crunch in the stack space (in 2.4), but in the absense of ideas to deal with it, the drivers had no choice but to constraint themselves in whatever was available. The thread_info made quite some room in the stack, and hence must have found its place in 2.6 Regards, Rajat -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
