From: Matthew Hall <mhall@mhcomputing.net>
To: Jay Rolette <rolette@infiniteio.com>
Cc: DPDK <dev@dpdk.org>
Subject: Re: [dpdk-dev] More KNI performance
Date: Fri, 5 Jun 2015 10:00:59 -0700 [thread overview]
Message-ID: <20150605170059.GA31882@mhcomputing.net> (raw)
In-Reply-To: <CADNuJVok_rqMs4da4=NUSpyFQ5mBZzvp1V6bytc4-moZW+AzXw@mail.gmail.com>
On Fri, Jun 05, 2015 at 10:27:21AM -0500, Jay Rolette wrote:
> Is there some mechanism available that the KNI kernel thread could sleep
> periodically, but somehow be awoken from user space?
This is wildly unvalidated, but futex and SysV semaphore appear to be
accessible from the kernel side. SysV semaphore sounds a bit cleaner for what
you're attempting.
http://stackoverflow.com/questions/17391276/shared-semaphore-between-user-and-kernel-spaces
> So far it looks like adding a syscall is about the only path to let a
> user-space app kick a kernel thread. I haven't gotten as far as figuring
> out the details to make sure this all works in practice.
Matthew.
prev parent reply other threads:[~2015-06-05 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 15:27 Jay Rolette
2015-06-05 17:00 ` Matthew Hall [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=20150605170059.GA31882@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=rolette@infiniteio.com \
/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).