From: zengxg14 <zengxg14-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: dev <dev-VfR2kkLFssw@public.gmane.org>
Subject: rx_eth_tx_burst not work in slave app.
Date: Fri, 19 Sep 2014 17:12:32 +0800 [thread overview]
Message-ID: <201409191712288256456@gmail.com> (raw)
Hi all.
I wrote a program to recv and send pkt at the same port.
First init the port then use below code to receive pkts and send pkts. It works OK.
Then I try the multi-process. I init the port in master app, and run the recv and send in slave spp.
In this mode rx_eth_tx_burst() always return 0.
while ( 1 ) {
int nb_rx, t;
int tmp;
nb_rx = rte_eth_rx_burst(1, 0, pkt_mbuf, BURST_COUNT);
if (nb_rx == 0) {
rte_delay_us(20);
continue;
}
t = 0;
while (t < nb_rx) {
tmp = rte_eth_tx_burst(1, 0, &pkt_mbuf[t], nb_rx - t);
t += tmp;
}
}
What I found is:
In single-process mode, the tx_pkt_burst is set to ixgbe_xmit_pkts_vec.
In multi-process mode, after the master app is up, it shows tx_pkt_burst is ixgbe_xmit_pkts_vec.
But when the slave app is runing, "perf top" shows ixgbe_xmit_pkts is runing, not the ixgbe_xmit_pkts_vec.
How can I make the slave app still call the ixgbe_xmit_pkts_vec?
zengxg
reply other threads:[~2014-09-19 9:12 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=201409191712288256456@gmail.com \
--to=zengxg14-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.