All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Invoking a system call from within the kernel
Date: Sun, 19 Nov 2017 10:50:21 +0100	[thread overview]
Message-ID: <20171119095021.GA20058@kroah.com> (raw)
In-Reply-To: <20171118190931.GA9566@localhost.hsd1.tn.comcast.net>

On Sat, Nov 18, 2017 at 02:09:31PM -0500, Demi Marie Obenour wrote:
> Async system calls move the thread pool to the kernel.  The kernel has
> system-wide information and perform optimizations regarding e.g.
> scheduling and threadpool size that userspace cannot.  Furthermore,
> the kernel threadpool threads have no userspace counterparts, so they
> avoid requiring a userspace stack or other data structures.

But they are not "free", you have to handle all of that within the
kernel now.  In a way to properly account for all resources and
contraints that is needed in order to correctly manage such logic.

> There was a previous attempt to implement async system calls using the
> AIO interface.  Linus rejected it on the basis that an async system call
> API should be more general.

Yes, please go look at those previous attempts and learn from why they
failed if you wish to try to attempt this again.  Don't ignore history :)

Best of luck, it should be some fun work.

greg k-h

      parent reply	other threads:[~2017-11-19  9:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16  2:16 Invoking a system call from within the kernel Demi Marie Obenour
2017-11-16  9:54 ` Greg KH
2017-11-18 18:15   ` Demi Marie Obenour
2017-11-18 18:44     ` valdis.kletnieks at vt.edu
2017-11-18 19:09       ` Demi Marie Obenour
2017-11-19  0:49         ` valdis.kletnieks at vt.edu
2017-11-19  9:50         ` Greg KH [this message]

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=20171119095021.GA20058@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 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.