kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Queries on bottom halves
Date: Sun, 2 Sep 2018 19:44:31 +0200	[thread overview]
Message-ID: <20180902174431.GA29480@kroah.com> (raw)
In-Reply-To: <237636.1535909947@turing-police.cc.vt.edu>

On Sun, Sep 02, 2018 at 01:39:07PM -0400, valdis.kletnieks at vt.edu wrote:
> On Sun, 02 Sep 2018 20:58:14 +0530, Abhinav Misra said:
> 
> > But if in new kernel this implementation is changed then why we need so
> > many options to defer the work as all of them are basically getting
> > executed in almost the same way.* In that case code running softirq,
> > tasklet, workqueue and kernel thread are all same ?*
> > If this is true then why we just remove all these these option and keep one
> > or two alternative.
> 
> -ENOPATCH
> 
> Often the gain from simplification isn't enough to motivate somebody to
> actually do all the work of coding and exhaustively testing the patch series.

Also, when switching to a different mechanism (or combining them), odd
things happen due to the fact that those different methods do work just
a little bit differently.

This was recently shown by some noticable slowdowns in some USB device
paths like cameras, when one low-level primative in one subsystem moved
from one type to another to try to "simplify" things.

So Valdis is right, the only way this could ever be done is if someone
does the work.  And it's a lot of non-trivial work to do...

greg k-h

  reply	other threads:[~2018-09-02 17:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-27 17:14 Queries on bottom halves Abhinav Misra
2018-08-27 18:31 ` Chinmay V S
2018-09-01  8:05   ` Abhinav Misra
2018-09-02 10:54     ` Larry Chen
2018-09-02 15:28       ` Abhinav Misra
2018-09-02 17:39         ` valdis.kletnieks at vt.edu
2018-09-02 17:44           ` Greg KH [this message]
2018-09-03  4:23         ` Larry Chen

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=20180902174431.GA29480@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).