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 4D74045948; Mon, 9 Sep 2024 10:32:39 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3DA7D40B9D; Mon, 9 Sep 2024 10:32:39 +0200 (CEST) Received: from mail-ed1-f53.google.com (mail-ed1-f53.google.com [209.85.208.53]) by mails.dpdk.org (Postfix) with ESMTP id AB8A740691 for ; Mon, 9 Sep 2024 10:32:37 +0200 (CEST) Received: by mail-ed1-f53.google.com with SMTP id 4fb4d7f45d1cf-5c26815e174so4143243a12.0 for ; Mon, 09 Sep 2024 01:32:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pantheon.tech; s=google; t=1725870757; x=1726475557; darn=dpdk.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=bLKGhnKkcfgpCORWdZIbT4iykJ8ZlizTUZ6OfmXB2M0=; b=JEhpF9YqJb0Piiy2Keec5zG+Jn2kGJS1ugEHH5To8fqP8v3rClJJedkQQsHX2nvdIO q3WUR6DhZ9zNodnwGOzi1ehc7/oS0X8Fl4+l6qw0Fmmc744B5wwcvtFUSiwB5nrzo9F4 wVK0KgEoW90zvk8Jug7rC82tmIz0ReMNhEh4/WXkeySF9+u4Fj91UlxbggMNlnas0JcA CxmXNg8pj8oSo+slOmDEWbnhAceOAt3TeTPm0o28FSNEVkA4H2cAcEAIDSm4Wu2fa0xT eUFmAC8arRjtcDJWPHIjS+6rIIIz9fnBj71TzptaKBNEEz99BoYo0qySNWPRanWwaxf0 5cjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725870757; x=1726475557; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=bLKGhnKkcfgpCORWdZIbT4iykJ8ZlizTUZ6OfmXB2M0=; b=kym//NdPWvzmSbiiLCOXw2VqPEgg4qhv9FOc9MAlYB7I08vkCd9p7d5AkJzlyCpJYU NmLkJ7SO+WsOMa4R5wybBSECfECv871xa/xR46865vAcxwyZ1JHdTNu9RT4sisSHh7Iw zP17CUv36XpMNcACNc53CKh6Z4Xnk6omN+xf3QTpwobt3trTwBCMH4it3fV2gDfTCLcJ 22M8iyWSuZNQfkAOdVR3OxxIofvrLAycI1YAfwPIshsREOz3BZ7mIwy2CWXXumw7lpzl hJxX29XCRZ/1SF1TJ6OQ3ouzT6VFJHvCKBZpFmaSJK3b9xPgWMC/Vjgq42nbdMnkAsv8 ZGmQ== X-Gm-Message-State: AOJu0YxjtJYpH9aya8HNOW4hXaRDWg52NekLcv8CMtFZaFEI6NFyZn2E 85edyxA+0FniwmJxN9z/PDc9oqgteEGlc820PaX+zfF77/T7c0pEPRVgQ/nimTI= X-Google-Smtp-Source: AGHT+IHAPM1HXTs5s6j2Rz8VnbbOB4FETlYBlVmpPhCPnFBq0EKt9ANN6wYpw+Pr3on0FAwZ93dYog== X-Received: by 2002:a05:6402:42c7:b0:5c2:7002:7d00 with SMTP id 4fb4d7f45d1cf-5c3e95354b8mr5144954a12.5.1725870757063; Mon, 09 Sep 2024 01:32:37 -0700 (PDT) Received: from [192.168.200.22] ([84.245.121.62]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-5c3ebd424e5sm2659381a12.10.2024.09.09.01.32.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 09 Sep 2024 01:32:36 -0700 (PDT) Message-ID: Date: Mon, 9 Sep 2024 10:32:35 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] app/testpmd: add L4 port to verbose output To: Luca Vizzarro , Stephen Hemminger , Alex Chapman Cc: dev@dpdk.org, Aman Singh , Jeremy Spewock , Honnappa Nagarahalli , Paul Szczepanek References: <20240815142051.531978-1-alex.chapman@arm.com> <20240815082209.5c2813bf@hermes.local> <64c84d76-f40e-4a1e-aee0-f06d29004d4d@arm.com> Content-Language: en-US From: =?UTF-8?Q?Juraj_Linke=C5=A1?= In-Reply-To: <64c84d76-f40e-4a1e-aee0-f06d29004d4d@arm.com> 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 On 16. 8. 2024 13:46, Luca Vizzarro wrote: > On 15/08/2024 16:22, Stephen Hemminger wrote: >> The verbose output is already too verbose. >> Maybe you would like the simpler format (which does include the port >> number) >> see the network packet dissector patches. > > Hi Stephen, > > Thank you for the reply you left to Alex's patch. This is actually quite > helpful. > > I've had a look at your patch series and the hexdump is actually quite > great for our purpose at DTS, as it will allow us to detect a preset > packet identifier in the payload. > > Unfortunately, your patch doesn't solve the problem that Alex is having. > He's currently writing up a test suite to test the RSS hash keys and the > respective queues to which the incoming packets are placed into. To > correctly match the packets to the queue and hash key, he needs a way to > identify them. We explored some solutions and the L4 port seemed to be > the most problem-free with the least effort. Using the payload is > probably best and you've already posted the required changes too. The > only problem is that your hexdump output does not print the required RSS > values. > > Would you be be keen to add these to your patch? Otherwise, do you have > any ideas and/or solutions to tackle this specific problem? > Hi Stephen, Do you have any advice for us? Thanks, Juraj > Thank you, > Luca Vizzarro