DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gal Sagie <gal.sagie@gmail.com>
To: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] sending and receiving packets
Date: Thu, 17 Oct 2013 14:01:28 +0200	[thread overview]
Message-ID: <CAG9LJa5UT7f93POnt4RWjK0cSUF8HObuxpYEhDy21unXRDxktw@mail.gmail.com> (raw)
In-Reply-To: <C7CE7EEF248E2B48BBA63D0ABEEE700C43EA664317@GUREXMB01.ASIAN.AD.ARICENT.COM>

Rump kernels is a flexible kernel architecture which runs in user space and
is a very interesting project, you can read more about it
here => http://www.netbsd.org/docs/rump/#rump-about
It is currently part of the NetBSD source tree.

A project was made to integrate Intel DPDK inside Rump kernel networking
layer. (in order to provide a networking stack and user space on top of
DPDK)
You can read more about it here =>
https://github.com/anttikantee/dpdk-rumptcpip

By using this you can run TCP Server inside rump kernel client and
interface with the physical port using DPDK.

Gopi, you didnt give enough information what exactly you are trying to do,
you can look at the examples in the dpdk-rumptcpip
maybe its best you first try to run them and see everything works.
In order to write a TCP server application on top of Rump kernel you either
need to use the rump system call API's (starts with rump_..) or
use the libhijack  (You can read more about it in the rump kernels page)

Gal


On Thu, Oct 17, 2013 at 2:36 PM, Prashant Upadhyaya <
prashant.upadhyaya@aricent.com> wrote:

> 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.
>
> ===============================================================================
>



-- 
Best Regards ,

The G.

  reply	other threads:[~2013-10-17 12:00 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
2013-10-17 12:01   ` Gal Sagie [this message]
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=CAG9LJa5UT7f93POnt4RWjK0cSUF8HObuxpYEhDy21unXRDxktw@mail.gmail.com \
    --to=gal.sagie@gmail.com \
    --cc=dev@dpdk.org \
    --cc=prashant.upadhyaya@aricent.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).