LQ Articles DiscussionThis forum is for the discussion of content posted to the Articles and Editorials section.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
LINUX KERNEL SERIES Author:Dinesh Ahuja Title:Linux Kernel Series: Linux Kernel Threads
The purpose of this article is to cover Linux implementation of kernel threads and how these kernel threads can be used in kernel modules. This article will show how a kernel thread can be put to use for a monitoring purpose.
Most of today's operating systems provide multi-threading support and linux is not different from these operating systems. Linux support threads as they provide concurrency or parallelism on multiple processor systems. Most of the operating systems like Microsoft Windows or Sun Solaris differentiate between a process and a thread i.e. they have an explicit support for threads which means different data structures are used in the kernel to represent a thread and a process.
Thanks but what is this? Is it s a copy from a book/doc?
I already wrote a documentation in steps myself. If you need it, email me.
A good engineer, needs to document it properly. Please do NOT copy and paste from some others work. It is against the ethics, read IEEE ethics online.
Open source, sharing information is cool. However, again, you MUST document in steps, make it clear, define platforms, kernel versions, any other info etc.
Thanks but what is this? Is it s a copy from a book/doc?
I already wrote a documentation in steps myself. If you need it, email me.
A good engineer, needs to document it properly. Please do NOT copy and paste from some others work. It is against the ethics, read IEEE ethics online.
Open source, sharing information is cool. However, again, you MUST document in steps, make it clear, define platforms, kernel versions, any other info etc.
I just want to thank you for this article, as a person with a growing interest in the topic, I found it extremely well written and informative. Thanks for taking the time to share this with the rest of us.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.