DPDK usage discussions
 help / color / mirror / Atom feed
From: Andriy Berestovskyy <aber@semihalf.com>
To: Jason Kwon <m43kwon@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] KNI multi-queue example?
Date: Mon, 4 Apr 2016 18:11:56 +0200	[thread overview]
Message-ID: <CAOysbxqKV1dWKbnUNE5Ns=FeK6pnV=DPS56D8yEm6pw6yBUfTA@mail.gmail.com> (raw)
In-Reply-To: <CAEo68aqsA-fxOP+Zrf9yxjFjpzOZQ6OfG1Muo2V1ku+4D6WUiA@mail.gmail.com>

Hi Jason,

On Fri, Mar 25, 2016 at 1:00 AM, Jason Kwon <m43kwon@gmail.com> wrote:
> Is there a KNI example for devices and
> drivers which support multiple queues per port?

I guess there is no such an example, please see below.

> Would such an implementation involve instantiating multiple KNI devices,
> each to be associated with a single RX/TX queue pair?  Or would it be
> possible to associate multiple RX/TX queues of a single port to a single
> KNI device?

Since KNI has just 1 RX/TX pair, for the NIC->KNI path you need to
modify kni_ingress() to iterate all the NIC RX queues and send all of
those packets to the KNI.

For the KNI->NIC path you need to modify kni_egress() to distribute
the packets received from the KNI to multiple NIC TX queues (say,
based on a hash).

Having said the above, most likely it will not get you any performance
gain, since I guess the bottleneck is KNI, not the NIC queues.

Regards,
Andriy Berestovskyy

  reply	other threads:[~2016-04-04 16:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25  0:00 Jason Kwon
2016-04-04 16:11 ` Andriy Berestovskyy [this message]
2016-06-08 22:59   ` Cliff Burdick
2016-06-09 11:44     ` Andriy Berestovskyy

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='CAOysbxqKV1dWKbnUNE5Ns=FeK6pnV=DPS56D8yEm6pw6yBUfTA@mail.gmail.com' \
    --to=aber@semihalf.com \
    --cc=m43kwon@gmail.com \
    --cc=users@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).