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 E404F4318A; Tue, 17 Oct 2023 11:45:07 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CF5D541144; Tue, 17 Oct 2023 11:45:07 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 650F440273 for ; Tue, 17 Oct 2023 11:45:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1697535906; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ZU2jVn72eoEhkmusJJpArigcrEmA+axKmuV6TsIwCTU=; b=PdNjNKxGNdFx359O1OBFYR6vG/1YZBwcp++OZAfxAlR4BWz+tx/hwlvBP/GxByqONYko15 AFaxveqSN7nlN1YHeyJJDQBGn7D7H3YTnHDm2WNYdWSbkNfB3QzC3P8BYplF4tJZ8u+m3N YSi4OTDAtNA829iMOK6BurXqrq7mLBg= Received: from mail-wr1-f71.google.com (mail-wr1-f71.google.com [209.85.221.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-649-57vD85s1PlGESn56QOdwEA-1; Tue, 17 Oct 2023 05:45:04 -0400 X-MC-Unique: 57vD85s1PlGESn56QOdwEA-1 Received: by mail-wr1-f71.google.com with SMTP id ffacd0b85a97d-32cbe54ee03so3388715f8f.1 for ; Tue, 17 Oct 2023 02:45:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697535903; x=1698140703; h=content-transfer-encoding:in-reply-to:subject:from:references:cc:to :content-language:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ZU2jVn72eoEhkmusJJpArigcrEmA+axKmuV6TsIwCTU=; b=KCn4Deo+HK4js2Y28j/N1V9c5I/uZiN4qeBDPf823mkG10aylOnd1gGL5yrvfSlmGr 3zyjqj9BRD4jlAe0FwEZmnk5hPkI6zhTpXKe/oA9J3AwBW66SPbxw0tYdwRKC8MCC7Hw BbM8F0eMwoF2BLFaO0+OGHT8ZyFV2/BdaTXuAntuKpwzWIO4Bit7I7X+c0yt+qXLwm1f GDoeUc6SOuXlpIhDLEaVyQbphvp5M4u+b9UxHMYQineHVEGiAXds3ATMcWe8DJ3ALaFU HqY1ev+91ZltFejoH9tJUNodua6STE9EKuwZvwQwY7GBmVy4O/COhbRV+dSwCm2Q5WBc tAoA== X-Gm-Message-State: AOJu0YzBgTrs4LK2KWpoS83k0xN63ypCG05+RalXLX1z1x3Qmh19q4YT AfKPUz5ul9013SU+1nVNNwd45qQxIVYgoUdCdjPvWY38B4aHxalzOa/Is/ERhAIPvh6a4ufaags ONHs= X-Received: by 2002:adf:f186:0:b0:32c:eeee:d438 with SMTP id h6-20020adff186000000b0032ceeeed438mr1659527wro.54.1697535903348; Tue, 17 Oct 2023 02:45:03 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEzJrF17kvDHLF2ZASQKTBC5RGYfe4Mf+hESQvQLsXuuET0IUgh+5bbYXD7agNO3YQQI/VKHg== X-Received: by 2002:adf:f186:0:b0:32c:eeee:d438 with SMTP id h6-20020adff186000000b0032ceeeed438mr1659506wro.54.1697535902931; Tue, 17 Oct 2023 02:45:02 -0700 (PDT) Received: from [192.168.0.36] ([78.19.74.205]) by smtp.gmail.com with ESMTPSA id t17-20020a05600001d100b0032da49e18fasm1295077wrx.23.2023.10.17.02.45.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 17 Oct 2023 02:45:02 -0700 (PDT) Message-ID: Date: Tue, 17 Oct 2023 10:45:00 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 To: "Tummala, Sivaprasad" , David Marchand , dpdk-techboard , Ferruh Yigit Cc: "bruce.richardson@intel.com" , "konstantin.v.ananyev@yandex.ru" , "dev@dpdk.org" , Thomas Monjalon References: <20230925151027.558546-1-sivaprasad.tummala@amd.com> From: Kevin Traynor Subject: Re: [PATCH] config/x86: config support for AMD EPYC processors In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 On 16/10/2023 06:20, Tummala, Sivaprasad wrote: > [AMD Official Use Only - General] > > Hi DPDK Techboard, > > Request to add this topic for discussion in the next techboard meeting. > Hi Sivaprasad, Are you or a representative (Ferruh?) able to attend the techboard meeting (3pm UTC Wednesday) to discuss this item? thanks, Kevin. > Thanks & Regards, > Sivaprasad > >> -----Original Message----- >> From: Tummala, Sivaprasad >> Sent: Monday, October 16, 2023 10:44 AM >> To: David Marchand >> Cc: bruce.richardson@intel.com; konstantin.v.ananyev@yandex.ru; dev@dpdk.org; >> dpdk-techboard ; Thomas Monjalon >> >> Subject: RE: [PATCH] config/x86: config support for AMD EPYC processors >> >> [AMD Official Use Only - General] >> >> Caution: This message originated from an External Source. Use proper caution >> when opening attachments, clicking links, or responding. >> >> >> [AMD Official Use Only - General] >> >>> -----Original Message----- >>> From: David Marchand >>> Sent: Friday, October 6, 2023 1:21 PM >>> To: Tummala, Sivaprasad >>> Cc: bruce.richardson@intel.com; konstantin.v.ananyev@yandex.ru; >>> dev@dpdk.org; dpdk-techboard ; Thomas Monjalon >>> >>> Subject: Re: [PATCH] config/x86: config support for AMD EPYC >>> processors >>> >>> Caution: This message originated from an External Source. Use proper >>> caution when opening attachments, clicking links, or responding. >>> >>> >>> On Mon, Sep 25, 2023 at 5:11 PM Sivaprasad Tummala >>> wrote: >>>> >>>> From: Sivaprasad Tummala >>>> >>>> By default, max lcores are limited to 128 for x86 platforms. >>>> On AMD EPYC processors, this limit needs to be increased to leverage >>>> all the cores. >>>> >>>> The patch adjusts the limit specifically for native compilation on >>>> AMD EPYC CPUs. >>>> >>>> Signed-off-by: Sivaprasad Tummala >>> >>> This patch is a revamp of >>> >> http://inbox.dpdk.org/dev/BY5PR12MB3681C3FC6676BC03F0B42CCC96789@BY5PR >>> 12MB3681.namprd12.prod.outlook.com/ >>> for which a discussion at techboard is supposed to have taken place. >>> But I didn't find a trace of it. >>> >>> One option that had been discussed in the previous thread was to >>> increase the max number of cores for x86. >>> I am unclear if this option has been properly evaluated/debatted. >>> >>> Can the topic be brought again at techboard? >> >> Hi David, >> >> The patch is intended to detect AMD platforms and enable all CPU cores by default >> on native builds. >> >> As an optimization for memory footprint, users can override this by specifying "- >> Dmax_lcores" option based on DPDK lcores required for their usecases. >> >> Sure, will request to add this topic for discussion at techboard. >>> >>> Thanks. >>> >>> -- >>> David Marchand >