dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Akshay <akshay.ranjan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: kuldeep.samasi-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.org
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: PMD architecture related to code
Date: Fri, 13 Mar 2015 10:48:01 +0530	[thread overview]
Message-ID: <CAEe8XATKVogEoSWcwUrTkBP4uKM12_vMqVeWVEf6LN2U4ZqKVw@mail.gmail.com> (raw)
In-Reply-To: <SIXPR03MB06056AFE877E1760ADD35EAB8A070-vZpGLg/9lRnmkicDWJed+682SN/2zMuYvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>

Kuldeep,

The documentation on 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-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.org> 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
>

  parent reply	other threads:[~2015-03-13  5:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  4:45 PMD architecture related to code kuldeep.samasi-uxC5H9eHYlcAvxtiuMwx3w
     [not found] ` <SIXPR03MB06056AFE877E1760ADD35EAB8A070-vZpGLg/9lRnmkicDWJed+682SN/2zMuYvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2015-03-13  5:18   ` Akshay [this message]
     [not found]     ` <CAEe8XATKVogEoSWcwUrTkBP4uKM12_vMqVeWVEf6LN2U4ZqKVw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-13 10:45       ` kuldeep.samasi-uxC5H9eHYlcAvxtiuMwx3w
     [not found]         ` <SIXPR03MB0605BCD7E1BC0533637AD8FB8A070-vZpGLg/9lRnmkicDWJed+682SN/2zMuYvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2015-03-13 10:57           ` Akshay
2015-03-13 14:51   ` Bruce Richardson
2015-03-14  7:52     ` kuldeep.samasi-uxC5H9eHYlcAvxtiuMwx3w
     [not found]       ` <SIXPR03MB0605384C3054BE0ABC56EF798A040-vZpGLg/9lRnmkicDWJed+682SN/2zMuYvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2015-03-17 13:03         ` ["Potential Spoofed"] " kuldeep.samasi-uxC5H9eHYlcAvxtiuMwx3w

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=CAEe8XATKVogEoSWcwUrTkBP4uKM12_vMqVeWVEf6LN2U4ZqKVw@mail.gmail.com \
    --to=akshay.ranjan-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=kuldeep.samasi-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.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).