DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sachin Sharma <sharonsachin@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Different core to each operation of packet handling
Date: Thu, 29 Jan 2015 18:02:10 +0100	[thread overview]
Message-ID: <CAH-Vi3wbmX2b_24kDuNddg3dVA=nb8cky5P1ZOyUUEW_PyvGiA@mail.gmail.com> (raw)

Hi all,


I am interested to assign different cores to each of the following
operations: (1) copying an incoming packet from NIC to the memory pool, (2)
handling the copied packet  from the userspace program (e.g., l2fwd
application), (3) doing lookup  for output port for the packet, (4)
transmitting the packet to the output NIC, (5) transmitting the packet from
NIC to the wire. I am able to do (2), (3), (4) by calling rte_eth_rx_burst
from a function assigned to a specific core (rte_eal_remote_launch), by
calling a lookup function that is assigned to another specific core, and by
calling rte_eth_tx_burst from a function (assigned to another core),
respectively. However, I do not know how to assign (1) and (5) operation to
a specific core. Could you please guide me for this?

Thanks,

                 reply	other threads:[~2015-01-29 17:02 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='CAH-Vi3wbmX2b_24kDuNddg3dVA=nb8cky5P1ZOyUUEW_PyvGiA@mail.gmail.com' \
    --to=sharonsachin@gmail.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).