From: Harish Patil <harish.patil@qlogic.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Inter-VM communication packet flow
Date: Thu, 24 Jul 2014 05:41:25 +0000 [thread overview]
Message-ID: <036FA1BC4A80D448AB7D9C3AAFBBCAF59F803BE0@AVMB1.qlogic.org> (raw)
In-Reply-To: <036FA1BC4A80D448AB7D9C3AAFBBCAF59F80364E@AVMB1.qlogic.org>
Gentle second request.
>DPDK-dev,
>From the documentation, its not very clear to me how would the inter-VM
>communication packet path (traffic crossing the physical port), especially
>the way macaddr table is populated in each PF port and role of the PF poll
>mode driver in this context. Could you please explain the flow here?
>
>Thanks,
>Harish
>
>
>
>
________________________________
This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message.
next prev parent reply other threads:[~2014-07-24 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 19:15 Harish Patil
2014-07-24 5:41 ` Harish Patil [this message]
2014-07-24 7:33 ` Thomas Monjalon
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=036FA1BC4A80D448AB7D9C3AAFBBCAF59F803BE0@AVMB1.qlogic.org \
--to=harish.patil@qlogic.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).