DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: "Olson, Matt Lyle" <matthew.lyl.olson@hp.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Running kni with low amount of cores
Date: Fri, 11 Jul 2014 02:53:09 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A74C02C@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <0262E9805BD2664BBA70725A838003031C86BD@G2W2432.americas.hpqcorp.net>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olson, Matt Lyle
> Sent: Thursday, July 10, 2014 4:12 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Running kni with low amount of cores
> 
> Hello,
> 
> I have two NIC devices and a quad core system that I'm trying to run kni on. I
> would like to leave two cores for general use and two cores for kni. When run
> kni on just one of the ports, everything works fine and I can use that vEth
> normally. The exact command I run is this: ./kni -c 0x0c -n 2 -- -P -p 0x1
> -config="(0,2,3)" But when I try to run kni on both ports, I can't find a
> configuration to make it work. Here's all the configs that I have tried, but none
> of them seem to work properly, the same way as just a single port: "(0,2,3),
> (1,2,3)"     "(0,2,3), (1,3,2)"    "(0,2,2), (1,3,3)". I'm wondering if it is
> supposed to work this way,  where each port needs its own Tx and Rx core, or
> if there is a way to get around it. If it is supposed to work this way, would it be
> worth my time to edit the code to allow me to have all Rx information dealt
> with on one core and all Tx on another?
> 
> Thanks,
> Matt Olson

Hi Matt

For the KNI example application, each lcore is used for RX or TX of a port only, you can check the first part of code in main_loop() in examples/kni/main.c.
It assumes that the number of lcores is not the bottle neck.

So for the scenario of yours, that might be supported. But it would not be too difficult to support your case by modifying the example application by yourself.

Regards,
Helin

      reply	other threads:[~2014-07-11  2:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 20:12 Olson, Matt Lyle
2014-07-11  2:53 ` Zhang, Helin [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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A74C02C@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=matthew.lyl.olson@hp.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).