Skip to content

Clarify tasklet limitations and deprecation plans #306

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 18, 2025
Merged

Clarify tasklet limitations and deprecation plans #306

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions lkmpg.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down Expand Up @@ -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.

Expand Down