From: Royce Niu <royceniu@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Request an example config for DPDK IP PIPELINE
Date: Mon, 25 Jan 2016 23:46:52 +0800 [thread overview]
Message-ID: <CAOwUCNuCz2e5sB6U9U1+p894BmEebyxaxo2T46zNNhLw+u9ZNg@mail.gmail.com> (raw)
In-Reply-To: <2104784.rzpFcqBxg0@xps13>
Hi, Thomas
I spent whole day finding them and you give me what I need in 10min.
Many Thanks.
Could you tell me how to send an patch on doc or the rule to send a patch.
I will add these for others.
On Mon, Jan 25, 2016 at 11:42 PM, Thomas Monjalon <thomas.monjalon@6wind.com
> wrote:
> 2016-01-25 23:40, Royce Niu:
> > I already bind three ports in DPDK. I want to set up a small router and a
> > firewall by IP Pipeline.
> >
> > But, I am so surprised that the doc (
> > http://dpdk.org/doc/guides/sample_app_ug/ip_pipeline.html) only provide
> the
> > format of config without a complete config. So, may I have an example
> > config of router/firewall file and I will modify my own config according
> to
> > the example config.
>
> I think you will find this directory helpful:
> http://dpdk.org/browse/dpdk/tree/examples/ip_pipeline/config
>
> Please do not hesitate to send a patch to add a line in the doc.
> Thanks
>
--
Regards,
Royce Niu
next prev parent reply other threads:[~2016-01-25 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 15:40 Royce Niu
2016-01-25 15:42 ` Thomas Monjalon
2016-01-25 15:46 ` Royce Niu [this message]
2016-01-25 15:58 ` Thomas Monjalon
2016-01-25 16:03 ` Royce Niu
2016-01-25 17:00 ` Singh, Jasvinder
2016-01-25 17:09 ` Royce Niu
2016-01-25 17:18 ` Singh, Jasvinder
2016-01-25 17:21 ` Royce Niu
[not found] ` <56AA0736.3080908@intel.com>
2016-01-28 14:14 ` Singh, Jasvinder
2016-01-28 14:26 ` Royce Niu
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=CAOwUCNuCz2e5sB6U9U1+p894BmEebyxaxo2T46zNNhLw+u9ZNg@mail.gmail.com \
--to=royceniu@gmail.com \
--cc=thomas.monjalon@6wind.com \
--cc=users@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).