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 3763B425C2; Sun, 17 Sep 2023 14:31:10 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B4572402B1; Sun, 17 Sep 2023 14:31:09 +0200 (CEST) Received: from forward500b.mail.yandex.net (forward500b.mail.yandex.net [178.154.239.144]) by mails.dpdk.org (Postfix) with ESMTP id 69AB340223; Sun, 17 Sep 2023 14:31:08 +0200 (CEST) Received: from mail-nwsmtp-smtp-production-main-92.myt.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-92.myt.yp-c.yandex.net [IPv6:2a02:6b8:c12:2028:0:640:9007:0]) by forward500b.mail.yandex.net (Yandex) with ESMTP id BC4215E891; Sun, 17 Sep 2023 15:31:07 +0300 (MSK) Received: by mail-nwsmtp-smtp-production-main-92.myt.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id 5Vi3ZmhW10U0-RSR7Ni7t; Sun, 17 Sep 2023 15:31:07 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1694953867; bh=/6aRnFSSHmHz0uqtaHpbpfjaSCpJh4GF4rN7+VuTJgA=; h=In-Reply-To:From:To:Date:References:Subject:Message-ID; b=B4A9krKC+ZWi+Ux5oDE33UjqK5B9jO2SgdrKSUGKWWBifk2XGFdUwfaPySuR2910a SVdAAp+B0xDD6I1y6jHH7oz7uQEKgs4bE/3b2zjqmBMyT1FsprOCgm6Wtfqbh/4ryx ZEWRKFrWg3/1UGb6Dl8tMXZ0tC+NiHc+/yeuKO2Y= Authentication-Results: mail-nwsmtp-smtp-production-main-92.myt.yp-c.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <69f22907-65ce-fc66-8a54-79d77fb4e8cc@yandex.ru> Date: Sun, 17 Sep 2023 13:31:05 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.0 Subject: Minutes of Technical Board Meeting, 2023-Sep-06 Content-Language: en-US References: To: "dev@dpdk.org" , "techboard@dpdk.org" From: Konstantin Ananyev In-Reply-To: X-Forwarded-Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 Minutes of Technical Board Meeting, 2023-Spetember-06 Members Attending ----------------- -Aaron -Bruce -Hemant -Jerin -Kevin -Konstantin (Chair) -Maxime -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 2023-September-20 @3pm UTC, and will be chaired by Maxime 1) Aaron: Intel test lab update - Intel test lab is up and running - To avoid such shortcomings in future, the plan is to duplicate Intel-Lab specific test-cases in UNH test lab. Right now it is on the stage of identifying such test-cases and required HW. 2) Jerin: Policy for trace point addtion is automated via devtools/checkpatches.sh and proposed in: https://patches.dpdk.org/project/dpdk/patch/20230307120514.2774917-2-adwivedi@marvell.com/ - Main idea: libraries that already instrumented with trace-points (cryptodev, ethdev, eventdev and mempool) will require trace-point to be present in their new public API functions. - General ACK from the TB members. 3) Thomas: Call for reviews for the patch-series: http://patchwork.dpdk.org/project/dpdk/list/?series=29438 Main changes: - Promote DPDK thread API to stable (help MSVC integration) - Reduce the usage of pthread functions inside DPDK code. (pthread_cancel and pthread locks still remain for now). - Remove 'attributes' parameter for rte_thread_create_control() function - public API change. 4) Ben: quick update on marketing activity - DPDK August newsletter is out: https://www.dpdk.org/monthly-newsletter-august-2023/?utm_content=263403350&utm_medium=social&utm_source=linkedin&hss_channel=lcp-33275771 - Update on last DPDk site activities and expected number of attendees for DPDK user-space event.