From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 4D9BA5A35 for ; Fri, 5 Jun 2015 19:03:19 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id DE9F880BD84; Fri, 5 Jun 2015 10:00:59 -0700 (PDT) Date: Fri, 5 Jun 2015 10:00:59 -0700 From: Matthew Hall To: Jay Rolette Message-ID: <20150605170059.GA31882@mhcomputing.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: DPDK Subject: Re: [dpdk-dev] More KNI performance X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2015 17:03:19 -0000 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.