DPDK patches and discussions
 help / color / mirror / Atom feed
From: Lazaros Koromilas <l@nofutznetworks.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] mempool: allow for user-owned mempool caches
Date: Tue, 14 Jun 2016 09:55:49 +0100	[thread overview]
Message-ID: <CAHPNE8ir0n=n2w1rS77MejS0ZwVjdYE5orTDk3=JzQYTFavWcw@mail.gmail.com> (raw)
In-Reply-To: <575EA52F.706@6wind.com>

Hi Olivier,

I have it in my queue, I'll do my best to have it before the deadline.

Thanks!
Lazaros.

On Mon, Jun 13, 2016 at 1:21 PM, Olivier Matz <olivier.matz@6wind.com> wrote:
> Hi Lazaros,
>
> On 05/11/2016 11:56 AM, Olivier MATZ wrote:
>> Hi Lazaros,
>>
>> Sorry for the late review. Please find some comments,
>> in addition to what Konstantin already said.
>>
>
> Will you have the time to send a v3 before the end of the
> integration deadline at the end of the week?
>
> I think it should be rebased on top of latest mempool series
> from David Hunt:
> http://dpdk.org/ml/archives/dev/2016-June/040897.html
>
> Regards,
> Olivier

      reply	other threads:[~2016-06-14  8:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04 15:43 Lazaros Koromilas
2016-04-04 15:43 ` [dpdk-dev] [PATCH v2 2/2] mempool: use bit flags instead of is_mp and is_mc Lazaros Koromilas
2016-04-05  9:24 ` [dpdk-dev] [PATCH v2 1/2] mempool: allow for user-owned mempool caches Lazaros Koromilas
2016-04-18 13:17 ` Ananyev, Konstantin
2016-04-19 15:39   ` Lazaros Koromilas
2016-04-19 15:56     ` Thomas Monjalon
2016-05-11  9:56 ` Olivier MATZ
2016-06-13 12:21   ` Olivier Matz
2016-06-14  8:55     ` Lazaros Koromilas [this message]

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='CAHPNE8ir0n=n2w1rS77MejS0ZwVjdYE5orTDk3=JzQYTFavWcw@mail.gmail.com' \
    --to=l@nofutznetworks.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=olivier.matz@6wind.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).