From: sejun.kwon at samsung.com
To: spdk@lists.01.org
Subject: [SPDK] 128k sequential read / write (fio) performance with spdk+vpp is not as good as the one with "kernel TCP"
Date: Fri, 14 Feb 2020 04:00:30 +0000 [thread overview]
Message-ID: <20200214040030.2820.84204@ml01.vlan13.01.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
Hello,
I'm working on SPDK library + VPP, because some report said that VPP reduces the overhead of network.
When I test with VPP (with mlx5 poll mode driver) and null device with spdk, 4k performance with VPP is much better than the default(kTCP).
But, 128k write performance with VPP is 30 percent lower than the one with kTCP.
The configuration when VPP starts is as below.
Is there anyone why 128k write performance with VPP is not good as kernel ?
I increase num-rx-desc and there is improvment, but it still lower than kernel.
Thanks in advance.
unix {
nodaemon
cli-listen /run/vpp/cli.sock
# cli-listen localhost:5002
full-coredump
}
session {
evt_qs_memfd_seg
}
dpdk {
dev 0000:03:00.0
{
}
}
socksvr {
# socket-name /tmp/vpp-api.sock
socket-name /run/vpp-api.sock
}
plugins {
plugin default { disable }
plugin dpdk_plugin.so { enable }
}
reply other threads:[~2020-02-14 4:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200214040030.2820.84204@ml01.vlan13.01.org \
--to=spdk@lists.01.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