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 59F71A0547 for ; Fri, 28 May 2021 08:52:09 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D1AC940143; Fri, 28 May 2021 08:52:08 +0200 (CEST) Received: from mail-qk1-f172.google.com (mail-qk1-f172.google.com [209.85.222.172]) by mails.dpdk.org (Postfix) with ESMTP id 3046F40040 for ; Fri, 28 May 2021 08:52:08 +0200 (CEST) Received: by mail-qk1-f172.google.com with SMTP id q10so3178568qkc.5 for ; Thu, 27 May 2021 23:52:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jcjzdts1PthDzfgNQxmkGK/9ZQH87fYJArdr8hDG6m8=; b=aTxYlTgmCmDYTnsNFdwZGbaoErhlEPqhqlWCChRcbgEs4k/OjUy6dryNqx45MeUV4h 9Tqc+cssIfgOjffUikhMeSvr2xQrJA1zcu7mUVyWVokitsU2ekP9FoqvktOKMzwsShhc T33sXLPsJyn/mRIxqbfF/RjZ22Jf8JnbUA1vgdJVnCMTvx0qJ6gZqtu0MApiWpbE7ydQ KLYFcZtNAIrLGnhuhFXZBHDz4Nc5KUnCOBLvaiOfXlCCqk6tuMNP+83MrkfiOv3W2Bko kBqtaO8skto/hUq+QlsTvUFkLaAG2JpCChq78F1euT5zKIQrTsH18O/UYWtBYUuG8FDn 3HQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jcjzdts1PthDzfgNQxmkGK/9ZQH87fYJArdr8hDG6m8=; b=O7bTKJDj3xhk3MwsbfcI4EAY9lvsUvENTBdccSsQK1ZdKdUvb6yQfSKPPiXuIbi74z x9wDKguHETFi4ErFpkNGE4mXR3riiHm2b9bJe5Rs1P7wEQrm/iGZzyMAuo2PXBptIAua tSLhksoc2VdtLBnnMFJIFZ6G10fpQsdXqO7en5px6k3kAPVb27WYBQ7VF+gZxvx1b3St q+EZRL2OaeMF4xw3X6T2PByjftH7iwl+lW1pMdi7scmLch/j8cnYd8eNsSm4/xuE4kXE EM/jejQQnpESkh99BViE8F9WzUac/H2DgexRizI74+qP3RLITkWXfuc71C3K7NE7k9Zy 89+w== X-Gm-Message-State: AOAM531j0kp6MbG1rtSZImO4OhaF4hw9DMxlzRwtnfYS5QFG7umvj1EX P9K9EBnLFg0MtrYaj7Mk5w+OxNvRDIlpHNPAUUM= X-Google-Smtp-Source: ABdhPJwANWktAWNOtfTiLNco0HK99WIjq9vMgs4wBYk/M207uMC1skxsTHwWBzGLpxha87+VWl3e2JDLgGEdtEXsvhQ= X-Received: by 2002:a37:4694:: with SMTP id t142mr2457674qka.265.1622184727616; Thu, 27 May 2021 23:52:07 -0700 (PDT) MIME-Version: 1.0 References: <20210527125703.059eeead@hermes.local> In-Reply-To: <20210527125703.059eeead@hermes.local> From: Muhammad Zain-ul-Abideen Date: Fri, 28 May 2021 11:51:56 +0500 Message-ID: To: Stephen Hemminger Cc: Raslan Darawsheh , madhukar mythri , users Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [dpdk-users] Issue with UDP based fragmented packets on Azure cloud X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" I wonder is there any way to bypass RSS for some IP flag values like mf, or frag_offset On Fri, May 28, 2021, 12:57 AM Stephen Hemminger wrote: > On Thu, 27 May 2021 15:40:57 +0000 > Raslan Darawsheh wrote: > > > Hi, > > > > > -----Original Message----- > > > From: users On Behalf Of madhukar mythri > > > Sent: Thursday, May 27, 2021 5:58 PM > > > To: users@dpdk.org > > > Subject: [dpdk-users] Issue with UDP based fragmented packets on Azur= e > > > cloud > > > > > > Hi, > > > > > > We are facing issue with UDP/IP based fragmented packets on Azure clo= ud > > > platform with Accelerated-Network enabled ports. > > > > > > UDP fragmented Rx packets were able to receive well on media ports. > But, > > > when two fragmented packet received, first fragment is received on > Queue- > > > 0 > > > and second fragment is received on Queue-1. Ideally all the > fragments(of > > > single large packet) should be received single queue based on RSS, so > that > > > we can re-assemble as single pkt and process it, which is working wel= l > in > > > other platforms on KVM hyper-visors(with I40evf NIC=E2=80=99s). > > > > > > I think, the as per RSS hash cacluation all the fragmented pkts shoul= d > > > reach on single-queue(because the 5-tuple hash value will be same), b= ut > > > this is not happening in-case of Azue VM's Why ? > > > > > > Does anybody faced similar issue, please let me know your suggestion. > > I guess it depends on the fragments themselves, > > If your first fragment contains a UDP header (the first frag in the > list) then the RSS hash will be on the full 5 tuble > > Src/dst IP and src/dst udp > > But, for the other frags you'll not get src/dst udp since they are not > present in the pkt. > > I guess you should be using only RSS On IP header to make all frags go > to the same queue. > > > > > Yes, and this is not unique to Azure or even the DPDK. > Fragmented packets do not have enough information (no UDP header in secon= d > fragment) > to do L4 RSS. > >