From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: KNI interface Date: Fri, 18 Jul 2014 17:13:48 -0700 Message-ID: <20140719001347.GA44840@localhost.localdomain> References: <036FA1BC4A80D448AB7D9C3AAFBBCAF59F801916@AVMB1.qlogic.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: "dev-VfR2kkLFssw@public.gmane.org" To: Harish Patil Return-path: Content-Disposition: inline In-Reply-To: <036FA1BC4A80D448AB7D9C3AAFBBCAF59F801916-yWqByQLCgs06wu3ARrlbmA@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Sat, Jul 19, 2014 at 12:08:35AM +0000, Harish Patil wrote: > Hello dpdk-dev, > Went thru=E2=80=99 couple of documentation but not very clear to me. Do= es using > KNI means handing over all the packets received/transmitted by the poll > mode driver to the linux stack or can it be controlled for the control > packets only ? What is the KNI use-case (besides ethtool) and what are = the > best options/choices/strategy to use poll mode driver for data path and > linux for control plane operations ? > Hi Harish, the packets to be sent to the kernel through the KNI interface is entirely under application control, so it can be limited to control path packets only. Indeed this is the primary expected use case for this module, as the KNI cannot deal with the kind of data rates that the PMDs can work with. Regards, /Bruce