From 58990f6b45925a2bab109f7681c97e9540f1980a Mon Sep 17 00:00:00 2001 From: Cheng-Yang Chou Date: Fri, 18 Apr 2025 06:57:59 +0800 Subject: [PATCH] Clarify tasklet limitations and deprecation plans Improve wording and grammar in the tasklet section. Reflect current discussion on tasklet deprecation and correct Linux kernel casing. --- lkmpg.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lkmpg.tex b/lkmpg.tex index a587873d..960cc842 100644 --- a/lkmpg.tex +++ b/lkmpg.tex @@ -1279,7 +1279,7 @@ \subsection{Manage /proc file with seq\_file} \item \url{https://kernelnewbies.org/Documents/SeqFileHowTo} \end{itemize} -You can also read the code of \src{fs/seq\_file.c} in the linux kernel. +You can also read the code of \src{fs/seq\_file.c} in the Linux kernel. \section{sysfs: Interacting with your module} \label{sec:sysfs} @@ -1921,7 +1921,7 @@ \subsection{Tasklets} Example tasklet init continues... Example tasklet ends \end{verbatim} -Although tasklet is easy to use, it comes with several drawbacks, and developers are discussing about getting rid of tasklet in linux kernel. +Although tasklet is easy to use, it comes with several drawbacks, and developers have been discussing their removal from the Linux kernel. The tasklet callback runs in atomic context, inside a software interrupt, meaning that it cannot sleep or access user-space data, so not all work can be done in a tasklet handler. Also, the kernel only allows one instance of any given tasklet to be running at any given time; multiple different tasklet callbacks can run in parallel.