DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alexander Kozyrev <akozyrev@nvidia.com>
To: Rajasekhar Pulluru <pullururajasekhar@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: Dpdk packet reception
Date: Mon, 13 Mar 2023 16:14:26 +0000	[thread overview]
Message-ID: <DM5PR12MB2405E82BA5CBCC00538E7746AFB99@DM5PR12MB2405.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAGA5_H5UsBQ3BZdU=yo3zuVwuF2mB_ucY5_w=FiTtq_w1e=htw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

Hi Rajasekhar, Power Management API can “put the CPU into optimized power state and monitor the Ethernet PMD RX descriptor address, waking the CPU up whenever there’s new traffic”.
Please take a look at the rte_power_monitor() and dpdk-l3fwd-power application example to see if it works for you. What platform do you use? It is only supported on recent Intel CPUs and ARMs.

Regards,
Alex

From: Rajasekhar Pulluru <pullururajasekhar@gmail.com>
Sent: March 10, 2023 15:57
To: dev@dpdk.org
Subject: Dpdk packet reception

Hi Team,

Would like to know if dpdk has a select(fd)/epoll(fd) like mechanism to wake-up the application (say rx-pthread) asynchronously upon packet reception without enabling rxq interrupts?

I can't afford to lose a cpu-core polling continuously to check for packets using rte_eth_rx_burst.And I only have 1 core to receive packets from multiple ports.I don't want to use usleep of fixed timeout between rte_eth_rx_burst api invocation, as it potentially could lead to packets being rx-missed in 1 or more ports.

Thanks & Regards,
Rajasekhar

[-- Attachment #2: Type: text/html, Size: 3637 bytes --]

  reply	other threads:[~2023-03-13 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 20:57 Rajasekhar Pulluru
2023-03-13 16:14 ` Alexander Kozyrev [this message]
2023-03-14 14:39   ` Rajasekhar Pulluru

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=DM5PR12MB2405E82BA5CBCC00538E7746AFB99@DM5PR12MB2405.namprd12.prod.outlook.com \
    --to=akozyrev@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=pullururajasekhar@gmail.com \
    /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).