On Thu, 2007-04-19 at 13:40 +0530, sandeep lahane wrote: > > > > 1. First it is mentioned that the kernel threads dont have any page in user > > > space and hence they dont deserve memory desriptor and page tables and in > > > the next line it says it needs some data such as page tables to access > > > kernel memory. What page table it is referring here?? Every process has its > > > own page table for mapping the virtual to physical address, why kernel > > > thread requires that? > > I think this has to do with the page faulting in vmalloc region, the > page faulting code updates the current page table from the master page > table. Please CMIIW. > I don't think so, the kernel thread is as sensitive as the kernel itself for the page faults. It _should not_ fault, unless ofcourse if its a vmalloc'ed area .. and that happens every other kernel path anyway.... so, it has nothing to do with accessing vmalloc'ed area. Its just that since the kernel thread is scheduled by the scheduler, it needs its own memory descriptor even to access the kernel memory.. And i think vivek has mentioned correctly about "whys and hows" about the kernel threads memory descriptors... cheers, sandeep -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
