From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <users-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 206EB46B8B
	for <public@inbox.dpdk.org>; Wed, 16 Jul 2025 14:45:27 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id EB6BF4021E;
	Wed, 16 Jul 2025 14:45:26 +0200 (CEST)
Received: from agw.arknetworks.am (agw.arknetworks.am [79.141.165.80])
 by mails.dpdk.org (Postfix) with ESMTP id 7ADA24013F
 for <users@dpdk.org>; Wed, 16 Jul 2025 14:45:25 +0200 (CEST)
Received: from debian (unknown [78.109.67.75])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by agw.arknetworks.am (Postfix) with ESMTPSA id 2DF4FE0976;
 Wed, 16 Jul 2025 16:45:24 +0400 (+04)
DKIM-Filter: OpenDKIM Filter v2.11.0 agw.arknetworks.am 2DF4FE0976
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arknetworks.am;
 s=default; t=1752669924;
 bh=HYP4XO7WJjNj7r6ukh/opKQyVh0CcY467etJZB3ibSY=;
 h=Date:From:To:cc:Subject:In-Reply-To:References:From;
 b=Ne+lc3iIpTXqiuCEvTz7UI3Rjv7LnYULRsy3qcn8MV+E8H6LhzNtWYq9CDmTpGZpn
 VDvV2/bgaiyRYcBisMWrAmgGNAz6leazVXyBhMaiCJBvGX1GhOMXip33NE4P456gGZ
 TEeAOEiVw5GCAg1ZmLi/KVNH1WldR+aRAd0TE9UeRM/M9Ihg4cR6p2vZ/M48jquCgw
 KvPNk/M3XcdY8cw59U1GP/3odj/EF3g4mrj1Xyfx4BZtPJrtiiSBSs2WunNkwYhxMt
 LmRj3bQTjnGYNfjY9cJZVFWvyqODpJlUphSFKZ6yWs+tUL+/Hzn7N8vZDdJY/E9Wr9
 ff4fcLY8HEjMA==
Date: Wed, 16 Jul 2025 16:45:07 +0400 (+04)
From: Ivan Malov <ivan.malov@arknetworks.am>
To: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
cc: users <users@dpdk.org>
Subject: Re: Rx performance
In-Reply-To: <CH3PR01MB847019A1426FDBCD8D4C3F0F8F56A@CH3PR01MB8470.prod.exchangelabs.com>
Message-ID: <07233a30-d3ba-0332-baf8-4a58c116af3a@arknetworks.am>
References: <CH3PR01MB847019A1426FDBCD8D4C3F0F8F56A@CH3PR01MB8470.prod.exchangelabs.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="8323328-1123617931-1752669924=:8596"
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
Errors-To: users-bounces@dpdk.org

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323328-1123617931-1752669924=:8596
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT

Hi Ed,

On Wed, 16 Jul 2025, Lombardo, Ed wrote:

> Hi,
> I have E810-C 2x100G NIC, the perf tool shows scalar rx path and not vectorized rx path.  When I turn off Rx Offload (NIC rx timestamp) I see vectorized rx path in perf tool.  
> 
> Why is this a drawback and is this with just the E810 NIC?

See the comment on line [1]. By the sound of it, this is somewhat expected.
[1] https://github.com/DPDK/dpdk/blob/fa3aca8a525decfd12bd5fa01ebc98789d5f7278/drivers/net/intel/common/rx.h#L104

Thank you.

> 
> is there a way around this so Rx Offload Rx Timestamp can be used in our application and get vectorized rx path?  
> 
> We need rx timestamps of packets and max performance.
> 
> Thanks,
> Ed
> 
>
--8323328-1123617931-1752669924=:8596--