All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reto Baettig <baettig@scs.ch>
To: "M.Kiran Babu" <kbabu@iitg.ernet.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: threads
Date: Fri, 10 Nov 2000 08:05:10 -0800	[thread overview]
Message-ID: <3A0C1CB6.BC7BE4AB@scs.ch> (raw)
In-Reply-To: <Pine.LNX.4.10.10011102031210.31929-100000@kamrup.iitg.ernet.in>

lock_kernel is a special case and will not block when you call it in
order to create a new kernel thread. Look at the implementation of
lock_kernel if you have any doubts (this is true for the 2.2 kernels. I
don't know it by heart for the 2.4 kernel). 

	Reto

"M.Kiran Babu" wrote:
> 
>  sir,
> i got some doubts in kernel
> programming. i am using linux 6.1 version. i want to use threads in
> kernel.is it possible to use pthreads in kernel. there is one more
> function kernel_thread. can i use
> that function. if i use that function how to get synchonization. inmany
> files it was used. but everywhere lock_kernel() and unlock_kernel()
> functions are being used. if we use that commands the whole kernel gets
> locked. is there any other mechanisms. or can i use that methods only. if
> i can use these methods what is the syntax of kernel_thread function. the
> arguments that are passing to these function are 3. i dont know what are
> those three. please  tell me.
> 
> 
> 
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-10 21:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-10 15:03 threads M.Kiran Babu
2000-11-10 15:39 ` threads Matti Aarnio
2000-11-10 16:05 ` Reto Baettig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-06 23:55 Ying Chen
2001-03-07  0:07 ` threads J . A . Magallon
2003-12-26 15:54 threads Albert Cahalan
2003-12-29 15:37 ` threads Stephen Smalley
2004-01-21  1:11   ` threads Albert Cahalan
2004-01-21  5:09     ` threads Russell Coker
2004-01-21 13:47     ` threads Stephen Smalley
2005-11-06  6:17 threads Fabio Andres Miranda
2005-11-06  8:41 ` threads Steve Graegert

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=3A0C1CB6.BC7BE4AB@scs.ch \
    --to=baettig@scs.ch \
    --cc=kbabu@iitg.ernet.in \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.