DPDK usage discussions
 help / color / mirror / Atom feed
From: yogesh purohit <yogesh.purohit@altencalsoftlabs.com>
To: users@dpdk.org
Subject: [dpdk-users] query related to DPDK-16.04  multi-process
Date: Tue, 04 Apr 2017 19:16:11 +0530	[thread overview]
Message-ID: <58E3A3A3.2010600@altencalsoftlabs.com> (raw)
In-Reply-To: <58E3A283.9020100@altencalsoftlabs.com>

  Hi,

    I am working on developing multiple DPDK-fastpath applications which 
would work as client-server model with some alterations over example of 
DPDK.

I would receive packet by Server application process it and pass it to 
client application and then return it to server. Server would be having 
complete control for packet Rx and Tx from the ports.

Can I have *multiple cores for running server application* and *each 
server application core can be binded with one client core* to it ??

Thanks & Regards,
Yogesh

           reply	other threads:[~2017-04-04 13:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <58E3A283.9020100@altencalsoftlabs.com>]

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=58E3A3A3.2010600@altencalsoftlabs.com \
    --to=yogesh.purohit@altencalsoftlabs.com \
    --cc=users@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).