Why cannot a generic void pointer be put in the task structure so that any one get to his private structure using this pointer? I have seen this kind of thing atleast in RTOSes where due to reentrancy the library functions needs to make copies of structures for every task; they simply hook pointer to these structures into the task structure. This makes things easy since u do not have to build individual tables and these tables are available to u readily when the task wakes up. My 2 cents Raghav Eduardo wrote: I can also know that files use tast_struct through the site lxr.linux.no. But, my doubt is that macros in assembly I must modify in the architecture i386 to be able to add an extra field tast_struct. I read something in http://www.geocrawler.com/archives/3/71/1997/3/0/89157/ (to architecture Sparc). In minix the equivalent to task_struct is the structure proc (src/kernel/proc.h). Shifts in this structure are defined in sconst.h so that routines in assembly have access it directly (as commentary of the book Operating System of Andrew Tanenbaum). Linux has something seemed? Where to get this type of information? Eduardo O Bode -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ IRC Channel: irc.openprojects.net / #kernelnewbies Web Page: http://www.kernelnewbies.org/
