From: Nikita Kozlov <nikita@gandi.net>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] lpm patches
Date: Mon, 1 Feb 2016 01:51:29 +0100 [thread overview]
Message-ID: <56AEAC11.602@gandi.net> (raw)
In-Reply-To: <20151030222524.GA23508@mhcomputing.net>
On 10/30/2015 11:25 PM, Matthew Hall wrote:
> On Fri, Oct 30, 2015 at 09:55:16PM +0000, Bruce Richardson wrote:
>> We'll see what we can do in 2.3 timeframe.
> Thanks for taking all of this up and helping us make a solid plan. I'll do my
> best to help out from the community side. I have done some lightweight
> functionality tests of my patched LPM to good effect.
>
> I'm working on finishing the last key feature and acquiring a Skylake system
> in the next few weeks so I can start doing some performance testing of my
> application with the community license of VTune, so I can make a proper
> release of some kind.
>
> Just so I know what things I should monitor when, what is the approximate
> schedule for 2.3? Can we host a private branch or tree somewhere to be able to
> access any progress made with the various changes and report back?
>
> Matthew.
Hello,
I wanted to know if there was something new or if I can help on this topic ?
I'm using rte_lpm in a project so I may (at least) do some tests or reviews.
next prev parent reply other threads:[~2016-02-01 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 12:00 Bruce Richardson
2015-10-30 17:59 ` Matthew Hall
2015-10-30 19:34 ` Vladimir Medvedkin
2015-10-30 21:55 ` Bruce Richardson
2015-10-30 22:25 ` Matthew Hall
2016-02-01 0:51 ` Nikita Kozlov [this message]
2016-02-01 21:21 ` Matthew Hall
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=56AEAC11.602@gandi.net \
--to=nikita@gandi.net \
--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).