Re: scheduler is a process and driver context?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jun 17, 2010 at 7:30 PM, Sudipta GHOSH <sudipta.in@xxxxxxxxx> wrote:
> Hi,
>
> Memory management , scheduling is part of core kernel.
>
> Is it a process or special code resides in RAM?
>
The entire kernel is special code that resides in RAM, hence the fact
it's a "monolithic" kernel.

> As I see init process has PID 0, so the kernel code is a process or
> special code.
It's simply special code. Think of it as a big chunk of privileged
functions that get called as needed.

>
> when there is an interrupt, device driver executes some code, in which context?
>
it's called "interrupt context", which happens to always run in
privileged mode. (e.g ring 0 in x86 CPUs)

> How data from userland to kernel space is transferred (user process to driver)
>
That's what system calls are for.

> Thanks,
> -S
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
> Please read the FAQ at http://kernelnewbies.org/FAQ
>
>

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux