From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id B6606A0C52; Wed, 24 Nov 2021 14:00:05 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5FDBE426D5; Wed, 24 Nov 2021 14:00:05 +0100 (CET) Received: from mail-wr1-f49.google.com (mail-wr1-f49.google.com [209.85.221.49]) by mails.dpdk.org (Postfix) with ESMTP id BCD6D41C3C for ; Wed, 24 Nov 2021 14:00:04 +0100 (CET) Received: by mail-wr1-f49.google.com with SMTP id j3so4112875wrp.1 for ; Wed, 24 Nov 2021 05:00:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind.com; s=google; h=date:from:to:subject:message-id:mime-version:content-disposition; bh=FZwnPg5XN23hf/fKCV0e5CsFEQQuJLBvhV3XdkXfgx4=; b=jD47I9tLGwOPVW60zmhv59fchXqYZ/UUaXpxeyzUzTbR85rjouug0kKPd0ITlax+8v pW9BDwBZIi3lK9zmZ6hiqM2NoN9Or6BazClnggE9zYB/orgtfmDDxZ1ayOm0ytl8T8o4 4CVgWacqyAxJ+1OlXqGoSHFbAHovATiH/rYTqUv47IrPtIfMGbBgdTwtCF7CJ7OsJ9nN gNcuIaB6MZNmvFpZyb1vgvIR+g3KWQJGMkxaa7raU9K/60qqNSnic8+IjQ5dKPYamnA3 5b4VPy3W3LB2Doeg+r8IXKqEilmf8+EpJAkx4BKQqFvMeGX3ZL9RPJJMYJmfwQ1ffjS9 whpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition; bh=FZwnPg5XN23hf/fKCV0e5CsFEQQuJLBvhV3XdkXfgx4=; b=cdG9PxxSBKck+LiW3wyulGJPYg5swgnNHFTMczqQdOVYlnBCbclyL7T9VRaQFpRDzK 7TtDCYmCdb2jEhYYOtdmA3rd3LjZJHFlTRWhYBtKmUpDyiTIyPwKcGxAVBjkTWMWLAJZ FriU1opwQ2e205ilFJbOyB8w4/pPshRMjPUbdySDN1pdy2CLdvRxy9YmCcoOyKH0QxsD KgSUVHr+3LD36Rh+13FRhjlM5Twsyn2Ro1irHRg1ghZ7g24Q9hsRVkCRJZHf00xMVUnG QnZxG0QreXwyRViA86byU2MFEG4AmW8Im4AcG4N6LnqiJB+B2OkM1Ng/ww9dRFnOewNn MZaA== X-Gm-Message-State: AOAM532l/VbahZlnDN9L4xrZid7ESZnaYyMRTsjTrvpQt8hCiR+l/iGn bnTGNwFzDJWVcgbMPpGCYZs4yRVfTxi/JQ== X-Google-Smtp-Source: ABdhPJzFqcsum9rxueECj8IgTZ+byb5++DFsvR2KKu13U9TrvUgCITkh2lb31H6uF+RE0OqEMLpU1w== X-Received: by 2002:a5d:6244:: with SMTP id m4mr18432320wrv.186.1637758804500; Wed, 24 Nov 2021 05:00:04 -0800 (PST) Received: from 6wind.com ([2a01:e0a:5ac:6460:c065:401d:87eb:9b25]) by smtp.gmail.com with ESMTPSA id u23sm4521746wmc.7.2021.11.24.05.00.03 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 24 Nov 2021 05:00:03 -0800 (PST) Date: Wed, 24 Nov 2021 14:00:03 +0100 From: Olivier Matz To: dev@dpdk.org Subject: Minutes of Technical Board Meeting, 2021-11-17 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Archived-At: List-Archive: Members Attending ----------------- - Aaron - Bruce - Ferruh - Honnappa - Jerin - Kevin - Konstantin - Maxime - Olivier (Chair) - Stephen - Thomas NOTE: The technical board meetings every second Wednesday at https://meet.jit.si/DPDK at 3 pm UTC. Meetings are public, and DPDK community members are welcome to attend. NOTE: Next meeting will be on Wednesday 2021-12-01 @3pm UTC, and will be chaired by Stephen. 1. Switch to 3 releases per year instead of 4 ============================================= Reference: http://inbox.dpdk.org/dev/5786413.XMpytKYiJR@thomas Only good feedback on the mailing list up to now. This proposal is therefore accepted - so DPDK will only have 3 releases in 2022 - unless there is strong opposition, with suitable justification, raised on the DPDK Dev mailing list ahead of the final DPDK 21.11 release. 2. Raise the maximum number of lcores ===================================== References: - https://inbox.dpdk.org/dev/1902057.C4l9sbjloW@thomas/ - https://inbox.dpdk.org/dev/CAJFAV8z-5amvEnr3mazkTqH-7SZX_C6EqCua6UdMXXHgrcmT6g@mail.gmail.com/ Modifying this value is an ABI change and has an impact on memory consumption. There is no identified use-case where a single application requires more than 128 lcores. - Ideally, this configuration should be dynamic at runtime, but it would require a lot of changes - It is possible with the --lcores EAL option to bind up to 128 lcores to any lcore id (even higher than 128). If "-l 129" is passed to EAL, a message giving the alternative syntax ("--lcores 0@129") is displayed. An option to rebind automatically could help for usability. - If a case a use-case exists for a single application that uses more than 128 lcores, the TB is ok to update the default config value. Note that it is already possible to change the value at compilation time with -Dmax_lcores in meson. 3. New threading API ==================== References: - https://patches.dpdk.org/project/dpdk/list/?series=20472&state=* - https://inbox.dpdk.org/dev/1636594425-9692-1-git-send-email-navasile@linux.microsoft.com/ The DPDK relies on the pthread interface for eal threads, which is not supported in windows. Windows DPDK code currently emulates pthread. A patchset has been proposed which, among others: - makes the eal thread API rely on OS-specific - removes direct call to pthread in dpdk This patchset (not for 21.11) needs more reviews. People from TB should take a look at it. The TB provided some guidelines: - the EAL thread API level should be similar to pthread API (it would mostly be a namespace change for posix) - the API/ABI should remain compatible. It is possible to make use of rte_function_versioning.h for that 4. DTS Co-maintenance ===================== Owen Hilyard from UNH proposes himself to be the co-maintainer for DTS. This would for instance help to ensure that the interface between CI and DTS remains stable. The TB welcomes this proposition, as long as there is no opposition from current DTS maintainer and DTS community. By the way, the TB asks for volunteers to help to make the transition to DPDK repository. 5. Spell checking in the CI infrastructure and patchwork ======================================================== The spell checking was done with aspell on documentation. The problem is that check is done on everything including code or acronyms, resulting on constant failures. The TB recommends to focus on per-patch basis checks, on rst files first. A tool should be provided in dpdk/devtools, so it can also be used by developpers. Spelling errors should be considered as warning given code or acronyms may trigger false-positives.