From: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
To: Gopi Krishna B <gopi97468@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] sending and receiving packets
Date: Thu, 17 Oct 2013 17:06:56 +0530 [thread overview]
Message-ID: <C7CE7EEF248E2B48BBA63D0ABEEE700C43EA664317@GUREXMB01.ASIAN.AD.ARICENT.COM> (raw)
In-Reply-To: <CA+XbSJKAeWdFnxhwfn9Ox7seMT2nBuXvv1Ag5kwawYCZ+LOPFw@mail.gmail.com>
Hi Gopi,
I have not worked with rumpkernel tcpip stack.
Does it run 'with' the DPDK in the userspace and is your tcp client application interacting over sockets to that tcpip stack in user space ?
If your stack is running in the kernel, then ofcourse you have to use a tap interface to interface with the kernel.
Can you describe your usecase in more details eg. what is the dpdk app, is the tcp client itself the dpdk app and so forth.
Normally, I use tcpclient/server as a normal linux kernel interfacing apps. I run a DPDK app and use a tap interface to switch packets in an out of the kernel. The kernel interacts over sockets with tcpclient/server as usual.
Regards
-Prashant
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Gopi Krishna B
Sent: Wednesday, October 16, 2013 8:13 PM
To: dev@dpdk.org
Subject: [dpdk-dev] sending and receiving packets
Hi,
I have DPDK 1.5 configured on my machine, I have also configured the rump kernel tcpip stack.
Now, to check whether the setup works, I started *TCP Server application*on another machine and connected the LAN cable to the port which is controlled by DPDK.
And I am running *TCP client application* on the machine having DPDK and rumpkernel tcpip stack.
The tcp client and server cannot communicate, is there some other configuration to be taken care for the traffic to flow appropriately on the machine running DPDK.
I have checked similar posts on the mailing list, but didnot get clue on how to debug the issue I am facing.
Any pointer/suggestions would be really of great help.
--
Regards
Gopi Krishna
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
next prev parent reply other threads:[~2013-10-17 11:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 14:42 Gopi Krishna B
2013-10-17 11:36 ` Prashant Upadhyaya [this message]
2013-10-17 12:01 ` Gal Sagie
2013-10-17 13:26 ` Gopi Krishna B
2013-10-17 15:27 ` Gal Sagie
2013-10-18 10:11 ` Gopi Krishna B
2013-10-18 10:40 ` Gal Sagie
2013-10-18 10:58 ` Gopi Krishna B
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=C7CE7EEF248E2B48BBA63D0ABEEE700C43EA664317@GUREXMB01.ASIAN.AD.ARICENT.COM \
--to=prashant.upadhyaya@aricent.com \
--cc=dev@dpdk.org \
--cc=gopi97468@gmail.com \
/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).