DPDK patches and discussions
 help / color / mirror / Atom feed
From: <kuldeep.samasi@wipro.com>
To: <akshay.ranjan@gmail.com>
Cc: dev@dpdk.org, dev-bounces@dpdk.org
Subject: Re: [dpdk-dev] PMD architecture related to code
Date: Fri, 13 Mar 2015 10:45:54 +0000	[thread overview]
Message-ID: <SIXPR03MB0605BCD7E1BC0533637AD8FB8A070@SIXPR03MB0605.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <CAEe8XATKVogEoSWcwUrTkBP4uKM12_vMqVeWVEf6LN2U4ZqKVw@mail.gmail.com>

Hi Akshay ,

I already gone through the DPDK prog guide , but I am wondering to know how Poll Mode driver working IN DPDK framework .




Regards
Kuldeep

From: Akshay [mailto:akshay.ranjan@gmail.com]
Sent: Friday, March 13, 2015 10:48 AM
To: Kuldeep Samasi (WT01 - Global Media & Telecom)
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] PMD architecture related to code

Kuldeep,

The documentation on dpdk.org<http://dpdk.org> explains quite a lot about the architecture. I suggest you go through it first.

http://dpdk.org/doc/guides/prog_guide/

-Akshay

On Fri, Mar 13, 2015 at 10:15 AM, <kuldeep.samasi@wipro.com<mailto:kuldeep.samasi@wipro.com>> wrote:
Hi Developer Team ,


I am trying add new functionality on Poll Mode driver .
But I don't have idea how packets are coming to kernel mode and going to user space and doing packet processing DPDK .

I need suggestion on which file the PMD architecture defined .



Regards ,
Kuldeep
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com>

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

  reply	other threads:[~2015-03-13 10:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  4:45 kuldeep.samasi
2015-03-13  5:18 ` Akshay
2015-03-13 10:45   ` kuldeep.samasi [this message]
2015-03-13 10:57     ` Akshay
2015-03-13 14:51 ` Bruce Richardson
2015-03-14  7:52   ` kuldeep.samasi
2015-03-17 13:03     ` [dpdk-dev] ["Potential Spoofed"] " kuldeep.samasi

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=SIXPR03MB0605BCD7E1BC0533637AD8FB8A070@SIXPR03MB0605.apcprd03.prod.outlook.com \
    --to=kuldeep.samasi@wipro.com \
    --cc=akshay.ranjan@gmail.com \
    --cc=dev-bounces@dpdk.org \
    --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).