you can communicate from 'ANY' task in user side to kernel side (probably an application talking to a driver), via ioctl calls..
PS. in case of android apps, android java app -> dalvik VM -(JNI)-> native library -(ioctl)-> kernel component On Thu, May 20, 2010 at 7:36 AM, xingchao wang <[email protected]> wrote: > hi, > > 2010/5/17 chungae9ri <[email protected]> > > Hi, all. >> Kernel is composed of many processes like kthreadd, ksoftirqd, ... >> so what is the process(task) of kernel which respond to the driver I/O >> control which is called from user space app? >> >> That's a mistake concept. > User space App communicates with Kernel driver by "open/read/write.." > device file. > There's no such special process(task) waiting to respond that. > > keroid > >> -- >> >> unsubscribe: >> [email protected]<android-porting%[email protected]> >> website: http://groups.google.com/group/android-porting >> > > > > -- > A Linux Kernel Android Developer > > -- > unsubscribe: > [email protected]<android-porting%[email protected]> > website: http://groups.google.com/group/android-porting > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
