[dpdk-dev] DPDK Community Survey - about to close
-Original Message- From: users [mailto:users-boun...@dpdk.org] On Behalf Of Glynn, Michael J Sent: Monday, August 29, 2016 6:14 PM To: users at dpdk.org; dev at dpdk.org; announce at dpdk.org Subject: [dpdk-users] FW: DPDK Community Survey - about to close > ... > > Regarding improvement areas, the main feedback was: > * Release Support (stable releases, LTS) > * Documentation - certain aspects are outdated and need attention > (particularly the Programmers Guide) > * No specific hotspots but performance bottlenecks seen in certain areas > * Need for a continuous integration and test environment Hi all - I just want to draw your attention to day 2 of the DPDK Userspace event in Dublin next week in which there will be a discussion on 'Usability (including packaging, stable releases, LTS releases etc.)' led by John McNamara (Intel), Christian Ehrhardt (Canonical), and Luca Boccassi (Brocade), and a presentation on 'Testing and Continuous Integration improvements in DPDK' by Qian Xu and Yuanhan Liu (both Intel). In addition, Bruce Richardson (Intel) will be giving a presentation on 'Identifying and Fixing Performance Bottlenecks in DPDK' using an example from the i40e driver illustrate the process. The full planned agenda is located here https://dpdksummit.com/
[dpdk-dev] FW: DPDK Community Survey - about to close
Hi all Firstly, thanks to all who provided input to the DPDK Community Survey. In total we had 149 responses with an 85% completion rate. ~40% of responders had contributed patches to a recent release which meant we had a good balance of contributors vs. users. In terms of what's working well, the high-level feedback was: * 96% of responders said that DPDK was meeting their requirements * Roadmap communications - timely and right level of detail. * Patch submissions process - 75% believe that it's working well * Release cadence - four releases per year seems to be the right amount * Engaged community - we got a significant amount of comments and feedback which we can use to drive further improvements Regarding improvement areas, the main feedback was: * Release Support (stable releases, LTS) * Documentation - certain aspects are outdated and need attention (particularly the Programmers Guide) * No specific hotspots but performance bottlenecks seen in certain areas * Need for a continuous integration and test environment I recently presented the results at the DPDK Summit so you can see more detail in this link https://dpdksummit.com/Archive/pdf/2016USA/Day02-Session15-MikeGlynn-DPDKSummit2016.pdf I'm also planning to share the full set of detailed feedback with the community which I'm collating at the moment. We are also planning to review the feedback at the Userspace event in Dublin with a view to discussing the improvement areas in particular. Finally, we are hoping to make this a regular survey (~every 6 months) to I'd like to encourage others to voice their opinions also! Regards, and thanks Mike -Original Message- From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Glynn, Michael J Sent: Thursday, August 4, 2016 11:09 AM To: dev at dpdk.org Subject: [dpdk-dev] FW: DPDK Community Survey - about to close Hi all Final reminder that the survey closes today Thanks to those who have already provided their input! Regards Mike
[dpdk-dev] FW: DPDK Community Survey - about to close
Hi all Final reminder that the survey closes today Thanks to those who have already provided their input! Regards Mike -Original Message- From: Thomas Monjalon [mailto:thomas.monja...@6wind.com] Sent: Tuesday, August 2, 2016 1:45 PM To: users at dpdk.org; dev at dpdk.org Cc: Glynn, Michael J Subject: Re: DPDK Community Survey - about to close Just 2 minutes for DPDK ;) http://surveymonkey.com/r/DPDK_Community_Survey 2016-08-02 14:39, Thomas Monjalon: > Hi all, > > That's the first time a DPDK survey is published. > It will help us in our future progress to decide what are the most > important stuff to work on. > > Please do not wait to fill it out. It closes on August 4. > Thanks for taking 2 minutes now to give your feedback. > When you will have done your duty, you might peacefully do your next > task or just enjoy a nice August month :) > > Each voice counts! Thanks > > > 2016-07-28 16:45, Glynn, Michael J: > > Hi all > > > > As part of our ongoing efforts to improve DPDK, we'd like to hear > > your feedback! > > > > We have created a number of DPDK-related questions here > > https://www.surveymonkey.com/r/DPDK_Community_Survey > > and want to hear your views!! > > > > The survey will close at midnight GMT on Thursday August 4th > > > > Thanks in advance for your feedback - the more responses we get the > > more data we have to drive further features, improvements, etc... > > so please respond!! > > > > Regards > > Mike >
[dpdk-dev] DPDK Community Survey
-Original Message- From: users [mailto:users-boun...@dpdk.org] On Behalf Of Glynn, Michael J Sent: Thursday, July 28, 2016 5:46 PM Hi all As part of our ongoing efforts to improve DPDK, we'd like to hear your feedback! We have created a number of DPDK-related questions here https://www.surveymonkey.com/r/DPDK_Community_Survey and want to hear your views!! The survey will close at midnight GMT on Thursday August 4th > Hi all > Just a reminder to submit your feedback by midnight GMT this Thursday, August > 4th > This is your opportunity to voice your feedback - the more we get the better > so appreciate if you can take a few minutes to respond using the link > provided. > Thanks to those who have already responded!! > Regards > Mike
[dpdk-dev] DPDK Community Survey
Hi all As part of our ongoing efforts to improve DPDK, we'd like to hear your feedback! We have created a number of DPDK-related questions here https://www.surveymonkey.com/r/DPDK_Community_Survey and want to hear your views!! The survey will close at midnight GMT on Thursday August 4th Thanks in advance for your feedback - the more responses we get the more data we have to drive further features, improvements, etc...so please respond!! Regards Mike
[dpdk-dev] DPDK Community Call - 16.04 Retrospective - Wednesday May 11th
Meeting Minutes for Community Call - May 11th 2014 Topic: DPDK 16.04 Retrospective Facilitators: Mike Glynn (Intel), John McNamara (Intel) Attendees: Christian Ehrhardt, Hemant Agrawal, Jan Viktorin, Mauricio Vasquez, Mike Holmes, Stephen Hemminger, Thomas Monjalon, Naoyuki Mori, Tom Gall, Konstantin Ananyev, Mike Glynn, John McNamara, Mohammad Abdul Awal, Bruce Richardson, Declan Doherty, Roy Fan Zhan, Ferruh Yigit, Bernard Iremonger, Reshma Pattan, Remy Horton, Vadim Sukhomlinov, Shanmukha Sreedhar Theerthala Minutes: * IRC chat channel was opened up the discussion (see notes captured below). IRC Channel: http://webchat.freenode.net/?channels=%23dpdk * John McNamara reviewed some statistics from 16.04, which included; o Number of commits per release - averaging ~700 o Number of contributors per release - ~100 for the past two releases o Unique "Reviewed-by" contributors is very low (7 in least release) o Number of "fix" patches - 301 o Number of patches with a "Fixes:" line - has grown from 45 in DPDK2.0 to 261 in 16.04 (attributed to greater compliance to using the "fixes" line) o Number of patchset revisions in v16.04 - vast majority at v1 (199) o Days between Author Date and Commit Date - 50% of final patches are merged within 7 days, 75% of final patches are merged within 14 days, "Final" patch means the last version, when all v1..vN comments have been addressed * Discussion on Areas for Improvement: o John Mc: 'Reviewed by' numbers are low. Thomas: this is likely because people don't distinguish between 'reviewed by' and 'acked'. Agreed that there is still value in retaining the reviewed-by tag. o Stephen H: Need more active reviews in the community. Suggested that the Maintainers could delegate to others on the mailing list. Maintainers - please take note. o Thomas M: Having a large number of v1's being applied may not be a good thing...would prefer to see higher number of patch revisions since it shows community review process is working better. Reviews are the area which require the most improvement. o Christian E: Packaging of DPDK - any community pushback to package something working almost everywhere but optimized where supported. No objections - Christian will post to the mailing list next week. http://udrepper.livejournal.com/20948.html o Documentation gaps in (1) RTE table library, and (2) ACL need to be addressed. Please discussion on the mailing list, submit patches, or ping John McNamara (documentation maintainer) o Mike G: Is the RFC process working? There is usually very little feedback on RFC's. Thomas commented that RFC's are still useful, suggested using header file (with Doxygen comments) as an RFC format. IRC Chat Notes: [16:09] == reshmapa [c0c6972b at gateway/web/freenode/ip.192.198.151.43] has joined #DPDK [16:16] Not enough public reviews [16:17] Fixes: lines are increasing (good for maintenance) [16:20] A lot of patches are committed late in the cycle [16:22] just for the minutes - since the call mentioned some missing commit stats - If I didn't mistype that should be 2.2 -> 16.04 - Authors: http://paste.ubuntu.com/16363502/ Domains: http://paste.ubuntu.com/16363543/ [16:29] == nijopa [~nijopa at 72.246.0.14] has quit [Quit: Leaving.] [16:33] == nijopa [~nijopa at 72.246.0.14] has joined #DPDK [16:35] not for minutes: audio quality is bad from some speakers - really hard to understand [16:36] == yliu [yliu131 at nat/intel/x-phwergujuqevebif] has joined #DPDK [16:39] I wanted at least see how the idea at all reflects with the community - http://udrepper.livejournal.com/20948.html [16:39] that would allow Distributions to package something working almost everywhere but optimized where supported [16:39] there were no hard opinions on it yet, I'll bring something to the mailing list (prob. next week) Please feel free to reply if I missed something/captured incorrectly
[dpdk-dev] DPDK Community Call - 16.04 Retrospective - Wednesday May 11th
Hi all Just a reminder about the 16.04 Retrospective Call tomorrow. All the call-in details are provided in Tim's email below Chat then! Mike -Original Message- From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of O'Driscoll, Tim Sent: Friday, April 29, 2016 3:09 PM To: dev at dpdk.org Subject: [dpdk-dev] DPDK Community Call - 16.04 Retrospective - Wednesday May 11th At the end of each release, we typically hold a retrospective within our development team to discuss what went well, what could be improved etc. For 16.04, we thought it would be a good idea to try doing this with the open source community, so that everybody involved in the project can provide their input and we can discuss any suggested improvements collectively. Mike Glynn, who's our Program Manager for DPDK, will facilitate the discussion. John McNamara has gathered some stats on things like how many revisions patches typically went through etc., which we'll present to help initiate the discussion, but the meeting should mostly be an open discussion where people should feel free to suggest any improvements they think we should make. If the approach is successful we can repeat it for future releases. When: London (United Kingdom - England)Wednesday, May 11, 2016 at 4PMBST UTC+1 hour San Jose (USA - California) Wednesday, May 11, 2016 at 8AMPDT UTC-7 hours Boston (USA - Massachusetts) Wednesday, May 11, 2016 at 11AM EDT UTC-4 hours Paris (France - ?le-de-France) Wednesday, May 11, 2016 at 5PMCEST UTC+2 hours New Delhi (India - Delhi)Wednesday, May 11, 2016 at 8:30PM IST UTC+5:30 hours Shanghai (China - Shanghai Municipality) Wednesday, May 11, 2016 at 11PM CST UTC+8 hours Tokyo (Japan)Midnight between Wednesday, May 11 and Thursday, May 12 JST UTC+9 hours GoToMeeting details: Please join my meeting from your computer, tablet or smartphone. https://global.gotomeeting.com/join/634498213 You can also dial in using your phone. United States : +1 (312) 757-3117 Access Code: 634-498-213 More phone numbers Australia : +61 2 8355 1039 Austria : +43 7 2088 1033 Belgium : +32 (0) 28 93 7001 Canada : +1 (647) 497-9379 Denmark : +45 69 91 89 33 Finland : +358 (0) 942 41 5770 France : +33 (0) 170 950 585 Germany : +49 (0) 692 5736 7303 Ireland : +353 (0) 19 030 050 Italy : +39 0 693 38 75 50 Netherlands : +31 (0) 208 080 208 New Zealand : +64 9 925 0481 Norway : +47 21 54 82 21 Spain : +34 911 82 9890 Sweden : +46 (0) 853 527 817 Switzerland : +41 (0) 435 0167 65 United Kingdom : +44 (0) 330 221 0099
[dpdk-dev] [PATCH v8 0/4] examples: add performance-thread
-Original Message- From: Betts, Ian Sent: Saturday, December 5, 2015 12:07 PM To: Thomas Monjalon; Stephen Hemminger Cc: dev at dpdk.org; O'Driscoll, Tim; Richardson, Bruce; Glynn, Michael J Subject: RE: [dpdk-dev] [PATCH v8 0/4] examples: add performance-thread -Original Message- From: Thomas Monjalon [mailto:thomas.monja...@6wind.com] Sent: Friday, December 4, 2015 6:34 PM To: Stephen Hemminger Cc: dev at dpdk.org; Betts, Ian Subject: Re: [dpdk-dev] [PATCH v8 0/4] examples: add performance-thread > Intel may have some milestone to get it into DPDK 2.2 but really this > seems too late... >>>Yes, sure it is too late to have enough discussions in 2.2 timeframe >Just to understand what we mean by too late... >The original RFC was issued on 2nd September. >Thus there have been some three months available for discussion, and for >people to raise any questions or concerns. >The first patch was available on 30th September, and a number of subsequent >patch versions have been issued, meaning the code has been available for >review for two month >As mentioned in the reply to Stephen, there has been no adverse feedback >during this period. >/Ian Hi Thomas/Stephen I agree with Ian, how much time is expected for a discussion to happen? As Ian stated, the feature was stated in our 2.2 planned feature list, we created a RFC over 3 months ago, and there's been code available for review for over 2 months now! (not to mention several version updates, docs, etc.). Given this, I believe that there has been ample time for the community to review and provide feedback rather than waiting until the eve of RC3 and then requesting more time. In addition, by making it a sample application first people can test it, see if it's useful, and further enhance it. Based on usefulness and feedback, we can then decide whether to make it a DPDK library in a future release, make it a separate library somewhere else, or do nothing further on it For these reasons, I believe it should be merged into RC3 Regards Mike
[dpdk-dev] [PATCH v3 0/8] add vhost TX offload support
Hi Thomas Is there anything else needed to get this applied? Thanks Mike -Original Message- From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Tan, Jianfeng Sent: Wednesday, November 4, 2015 11:14 AM To: Liu, Jijiang; dev at dpdk.org Subject: Re: [dpdk-dev] [PATCH v3 0/8] add vhost TX offload support > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jijiang Liu > Sent: Wednesday, November 4, 2015 6:54 PM > To: dev at dpdk.org > Subject: [dpdk-dev] [PATCH v3 0/8] add vhost TX offload support > > Adds vhost TX offload support. > > The patch set add the negotiation between us-vhost and virtio-net for > vhost TX offload(checksum and TSO), and add the TX offload support in > the libs and change vhost sample and csum application to test these changes. > > v3 change: > rebase latest codes. > . > lib/librte_vhost/virtio-net.c |6 ++- > 8 files changed, 302 insertions(+), 20 deletions(-) > > -- > 1.7.7.6 Acked-by: Jianfeng Tan
[dpdk-dev] [PATCH 00/34] update e1000 base driver
-Original Message- From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Lu, Wenzhuo Sent: Tuesday, October 20, 2015 2:00 AM To: Thomas Monjalon Cc: dev at dpdk.org Subject: Re: [dpdk-dev] [PATCH 00/34] update e1000 base driver > -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Tuesday, October 20, 2015 12:03 AM > To: Lu, Wenzhuo > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH 00/34] update e1000 base driver > > Hi Wenzhuo, > > Isn't it too late to have it included in DPDK 2.2? > For reference: http://dpdk.org/dev/roadmap Hi Thomas This is an update not a roadmap feature therefore I think it should be applied in 2.2 Regards Mike
