From: Moon-Sang Lee <sang0627@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] ksoftirqd when using KNI
Date: Fri, 25 Sep 2015 14:03:32 +0900 [thread overview]
Message-ID: <CAACK=XdFL-2jH=zN1-VZh687Y6VtiL67kU4G8W2vsHcnfY9aig@mail.gmail.com> (raw)
In-Reply-To: <CAACK=XdGSLido1Dqb1cbmx-w6Ng-0VswSPFK0hmuSfz2EwPs5Q@mail.gmail.com>
I've observed CPU stats with top command, and found that ksoftirqd
is processing software interrupts which might come from dpdk-kni application
and would be processed by KNI and kernel net stack.
My observation shows that
1. dpdk-kni-application drops a half of rx packets (i.e. fail to deliver
packets to skb).
this seems the rx_q is full in KNI side. I think this is because
processing in
KNI and IP stack is much slow and receiving packets from device via
dpdk is
much faster.
2. bonding multiple KNI interfaces to spread loads across multiple kernel
threads
does not help reduce that processing time. In addition, packets are
transmitted
out of order throughout multiple KNIs, which requires reordering
at the communication end point.
3. NAT with native kernel performs twice better than that of KNI + native
kernel
even though the latter does not incur hardware interrupts.
Anyway, my experiment was done in limited environment, so this does not
reflect
any general case.
My wish for simple NAT solution seems not feasible with KNI,
thus I should change my approach from KNI to pure dpdk application.
On Fri, Sep 18, 2015 at 8:53 PM, Moon-Sang Lee <sang0627@gmail.com> wrote:
>
> I'm a newbie and testing DPDK KNI with 1G intel NIC.
>
> According to my understanding of DPDK documents,
> KNI should not raise interrupts when sending/receiving packets.
>
> But when I transmit bunch of packets to my KNI ports,
> 'top command' shows ksoftirqd with 50% CPU load.
>
> Would you give me some comments about this situation?
>
>
>
> --
> Moon-Sang Lee, SW Engineer
> Email: sang0627@gmail.com
> Wisdom begins in wonder. *Socrates*
>
--
Moon-Sang Lee, SW Engineer
Email: sang0627@gmail.com
Wisdom begins in wonder. *Socrates*
prev parent reply other threads:[~2015-09-25 5:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 11:53 Moon-Sang Lee
2015-09-25 5:03 ` Moon-Sang Lee [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='CAACK=XdFL-2jH=zN1-VZh687Y6VtiL67kU4G8W2vsHcnfY9aig@mail.gmail.com' \
--to=sang0627@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).