From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] New RC needed for stablility?
Date: Wed, 2 May 2018 11:35:18 +0100 [thread overview]
Message-ID: <7db7ef55-1d10-502c-73c9-4ac78f7f1162@intel.com> (raw)
In-Reply-To: <4994002.UncbAHUyZt@xps>
On 4/30/2018 2:02 PM, Thomas Monjalon wrote:
> 30/04/2018 14:57, Bruce Richardson:
>> Hi Thomas, Ferruh, all,
>>
>> Initial testing on RC1 from our System Test and Validation shows a lot of
>> defects/issues, and from the list it appears others may be seeing issues
>> too. These issues, as well as causing test failures are blocking other
>> tests from being run. We are also seeing some serious performance
>> regressions with testpmd.
>>
>> Based on the number of issues we are seeing, which is probably a result of
>> the huge number of changes in this release even at the RC1 point, I would
>> propose that we look to do a new RC some time this week to get as many
>> critical bugs as possible ironed out, before we add in the remaining 18.05
>> features. That is: *bug-fix only* RC2, say Wed/Thurs (or sooner if fixes
>> are ready), with remaining features in RC3 as planned on 11th.
>>
>> Thoughts, comments?
>
> OK +1
>
> We need to agree on a list of bugs to be fixed.
The issues worked on for the rc2 is as following:
- Deadlock caused on eal by control threads
- Virtio memory issue.
- Several sample apps gives error because of rte_eth_dev_configure(),
dev_info.flow_type_rss_offloads check.
- 32bits DPDK applications are broken
> Are there some Bugzilla entries?
> When they will be fixed, I will tag the RC2.
prev parent reply other threads:[~2018-05-02 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 12:57 Bruce Richardson
2018-04-30 13:02 ` Thomas Monjalon
2018-05-02 10:35 ` Ferruh Yigit [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=7db7ef55-1d10-502c-73c9-4ac78f7f1162@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).