DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [RFC 1/1] eventdev: add distributed software (DSW) event device
Date: Thu, 23 Aug 2018 22:08:04 +0200	[thread overview]
Message-ID: <74b543df-e8fa-e44d-cf27-3597b37b34b5@ericsson.com> (raw)
In-Reply-To: <20180823134430.GA16161@jerin>

On 2018-08-23 15:44, Jerin Jacob wrote:
> -----Original Message-----
>> Date: Thu, 23 Aug 2018 15:08:29 +0200
>> From: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
>> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
>> CC: dev@dpdk.org, bruce.richardson@intel.com
>> Subject: Re: [dpdk-dev] [RFC 1/1] eventdev: add distributed software (DSW)
>>   event device
>> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
>>   Thunderbird/52.9.1
>>
>>
>> On 2018-08-19 08:11, Jerin Jacob wrote:
>>> I would like to include this driver for v18.08. Please send the next
>>> the version in order to complete review before giving RC1 pull request.
>>>
>>
>> I've been working on a test bench with real packet I/O and some more
>> reasonable load to verify load balancing behavior and tune some
>> parameters to let it have a chance to perform in a real-world application.
>>
>> Currently, the only experience comes from a pipeline simulator without
>> real I/O, and where new packets are always available, plus some very
>> limited experience from a prototype integration in a real product.
>>
>> All this to feel somewhat comfortable it will perform in a product.
>>
>> I think 18.08 will be difficult. When would you need to have something
>> ready to meet that deadline?
> 
> It is OK to postpone to v19.02 if it is difficult.
> 
> According to https://core.dpdk.org/roadmap/, The integration deadline for v18.11 is October 5, 2018.
> Considering it only driver change, two/three weeks would be enough to review it. So September mid
> would be a reasonable target.

OK, sounds like 18.11 might be doable. Thanks. Do you mark drivers 
experimental, just to warn people there might be dragons? Or is that 
just APIs?

I've been planning to run it on a system with a weak memory model, too. 
If someone want to help out here, that would be appreciated.

  reply	other threads:[~2018-08-23 20:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180711210844.5467-1-mattias.ronnblom@ericsson.com>
     [not found] ` <20180711210844.5467-2-mattias.ronnblom@ericsson.com>
2018-07-22 11:32   ` Jerin Jacob
2018-08-19  6:11     ` Jerin Jacob
2018-08-23 13:08       ` Mattias Rönnblom
2018-08-23 13:44         ` Jerin Jacob
2018-08-23 20:08           ` Mattias Rönnblom [this message]
2018-08-27  9:23     ` Mattias Rönnblom
2018-08-27  9:40       ` Jerin Jacob
2018-08-27 10:24         ` Mattias Rönnblom
2018-07-11 21:21 [dpdk-dev] [RFC 0/1] A Distributed Software Event Device Mattias Rönnblom
2018-07-11 21:21 ` [dpdk-dev] [RFC 1/1] eventdev: add distributed software (DSW) event device Mattias Rönnblom

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=74b543df-e8fa-e44d-cf27-3597b37b34b5@ericsson.com \
    --to=mattias.ronnblom@ericsson.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.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).