DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] imissed in rte_pmd_pcap
@ 2016-09-12  6:44 Keren Hochman
  2016-09-12 15:12 ` Ferruh Yigit
  0 siblings, 1 reply; 2+ messages in thread
From: Keren Hochman @ 2016-09-12  6:44 UTC (permalink / raw)
  To: dev

Hello,
in the dpdk pcap driver, the imissed indicator of rte_eth_stats structure
is not increasing even when we miss packets since there are no available
mbufs. I looked at the code and I saw that nothing increase it in the pcap
driver code ( as opposed to other drivers where it's being promoted)
Is there a reason for that? Is there other way to follow missed packets
when using libpcap ?
Thanks, Keren

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [dpdk-dev] imissed in rte_pmd_pcap
  2016-09-12  6:44 [dpdk-dev] imissed in rte_pmd_pcap Keren Hochman
@ 2016-09-12 15:12 ` Ferruh Yigit
  0 siblings, 0 replies; 2+ messages in thread
From: Ferruh Yigit @ 2016-09-12 15:12 UTC (permalink / raw)
  To: Keren Hochman, dev

Hi Keren,

On 9/12/2016 7:44 AM, Keren Hochman wrote:
> Hello,
> in the dpdk pcap driver, the imissed indicator of rte_eth_stats structure
> is not increasing even when we miss packets since there are no available
> mbufs. I looked at the code and I saw that nothing increase it in the pcap
> driver code ( as opposed to other drivers where it's being promoted)

As you said, it is not implemented, any patch welcome.

> Is there a reason for that?

No specific reason as far as I know.


> Is there other way to follow missed packets
> when using libpcap ?
> Thanks, Keren
> 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-09-12 15:12 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-09-12  6:44 [dpdk-dev] imissed in rte_pmd_pcap Keren Hochman
2016-09-12 15:12 ` Ferruh Yigit

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).