From: Jesse Pollard <pollard@admin.navo.hpc.mil>
To: Prasad <prasad_s@students.iiit.net>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Resending] User Process and a Kernel Thread
Date: Tue, 11 Mar 2003 12:04:48 -0600 [thread overview]
Message-ID: <200303111204.48708.pollard@admin.navo.hpc.mil> (raw)
In-Reply-To: <Pine.LNX.4.44.0303112306530.26279-100000@students.iiit.net>
On Tuesday 11 March 2003 11:37 am, Prasad wrote:
> Resending the mail...
>
> Hi all,
> Whats the difference between the user process and a kernel thread?
Kernel process/thread has access to all hardware capability. No security can
be envorced.
User process is limited to the memory the kernel allocates to the process. No
direct device access, no access to all system resources. All hardware access
is mediated by the kernel. Some privileged operations can be delegated to a
user process (see X server running without frame buffer support).
> IS it possible to make the kernel thread a user process?
No
>if yes, how do we
> do that?
>
> Prasad.
--
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
prev parent reply other threads:[~2003-03-11 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 17:37 Prasad
2003-03-11 18:04 ` Jesse Pollard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200303111204.48708.pollard@admin.navo.hpc.mil \
--to=pollard@admin.navo.hpc.mil \
--cc=linux-kernel@vger.kernel.org \
--cc=prasad_s@students.iiit.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®