DPDK patches and discussions
 help / color / mirror / Atom feed
From: Daniel Kaminsky <daniel.kaminsky@infinitelocality.com>
To: cr singh <cr.singh200@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] regarding KNI
Date: Thu, 2 Jan 2014 12:20:18 +0200	[thread overview]
Message-ID: <CA+8v-JxxSEMGq4eUTZ8m265SNe5-Gr+1tZjae0xpAvEQssxpkw@mail.gmail.com> (raw)
In-Reply-To: <CA+Rn91O9yQ+WMz5=RKURKuNBy_L7e=Mo1CUpT=wYkT0QT3+bWA@mail.gmail.com>

Hi C R,

This is a limitation of the KNI example and not of the DPDK package. The
current KNI example can use one core for single task - Egress/Ingress on
one port.

You definitely can change it, look into *main_loop *function.

Regards,
Daniel Kaminsky


On Thu, Jan 2, 2014 at 11:32 AM, cr singh <cr.singh200@gmail.com> wrote:

> hello devs,
>
> I am using DPDK 1.5.0 and trying to use KNI interface to measure throughput
> through it
>
>
>
> ------------------------------------------------------------------------------------------------------------
> I have machine with 2 lcores and 2 physical interface, and in running kni
> sample application --config parameter we are supposed to give
> 1)port no,
> 2)lcore_rx,
> 3)lcore_tx, right?
>
> so can it be possible to give same lcore no. for both ports, like
>
> kni -c 0x3 -n 4 -- -P -p 0x3 --config"(0,0,1),(1,0,1)"
>
> As i have tried and after running this two interface vEth0 and vEth1 is
> created, but when i am giving ip with ifconfig to vEth1 then it is showing
> the below message ...
>
> SIOCSIFFLAGS: Timer expired,
>
> while i am able to bring up the the vEth0 interface successfully.
>
>
> -----------------------------------------------------------------------------------------------------
> i am pasting some details which prints while running the application ...
>
> Checking link status
> .....done
> Port 0 Link Up - speed 1000 Mbps - full-duplex
> Port 1 Link Up - speed 1000 Mbps - full-duplex
> APP: Lcore 1 is writing to port 0
> APP: Lcore 0 is reading from port 0
>
>
> and here in last two line Lcore 1 and Lcore 0 is writting and reading for
> port 0 and may be therefore i am able to bring up the vEth0. and there is
> no core for port 1 so it is failing.
>
>
> ---------------------------------------------------------------------------------------------------------
>
> So my question is why can't we use same lcores for reading and writing  for
> both ports, does DPDK restricts using same lcores for 2 ports (as it
> seems), and if so, then why??
>
>
>
> Thanks in advance
> C R
>

      reply	other threads:[~2014-01-02 10:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02  9:32 cr singh
2014-01-02 10:20 ` Daniel Kaminsky [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=CA+8v-JxxSEMGq4eUTZ8m265SNe5-Gr+1tZjae0xpAvEQssxpkw@mail.gmail.com \
    --to=daniel.kaminsky@infinitelocality.com \
    --cc=cr.singh200@gmail.com \
    --cc=dev@dpdk.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 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).