From: Jan Kiszka <jan.kiszka@siemens.com>
To: dev@dpdk.org
Subject: [dpdk-dev] vhost-switch example: huge memory need and CRC off-loading issue
Date: Fri, 7 Aug 2015 19:31:08 +0200 [thread overview]
Message-ID: <55C4EB5C.4080001@siemens.com> (raw)
Hi again,
two findings in the vhost-switch example code that can cause grey hair
for starters:
- MAX_QUEUES of 512 causes pretty high memory need for the application
(something between 1 and 2G) - is that really needed? I'm now running
with 32, and I'm able to get away with 256M. Can we tune this
default?
- hw_strip_crc is set to 0, but either the igb driver or the ET2 quad
port adapter I'm using is ignoring this. It does strip the CRC, so
does software, and I'm losing 4 bytes on each unpadded packet. Known
issue?
Thanks,
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next reply other threads:[~2015-08-07 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 17:31 Jan Kiszka [this message]
2015-08-08 0:39 ` Ouyang, Changchun
2015-08-08 7:17 ` Jan Kiszka
2015-08-09 8:56 ` Thomas Monjalon
2015-08-10 1:10 ` Ouyang, Changchun
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=55C4EB5C.4080001@siemens.com \
--to=jan.kiszka@siemens.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).