From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f181.google.com (mail-pf1-f181.google.com [209.85.210.181]) by dpdk.org (Postfix) with ESMTP id 2DFED7CBC for ; Sat, 20 Oct 2018 03:59:10 +0200 (CEST) Received: by mail-pf1-f181.google.com with SMTP id r64-v6so17226891pfb.13 for ; Fri, 19 Oct 2018 18:59:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:mime-version:to:from:subject:date:importance; bh=WwOsRp5BzU0pXPqzjO9ez2yyAnUXX2mEX82eeUxMu0A=; b=eR3lBXbIU1vacFs7KVzZsvEnoANBNSn9agVkN4bORfbRHIX67r2t3FkwbkCge1XNxW +B5FHjKcNeEWD4czLgES2FJ/ziV+0gQT0egL4/44NKs8VHTml5RDHminUvQvi4jtUu9P mpyslrR2uWdkLdjJzfEmM+6E2IGSP9x4nFAlZClbBFGaih6rFAN5obn1kJBvo/tvL6v7 jvezpsS2XGmUG4Taf1M47YgC1J9mC6NA3B78lm9mpRCuyxhHbTAH4wp5vNxKzGzD5V+c HxamDCz/bZCpNh/ZqkCbJK7URG3qqdZslPyYKBaeHDwyHjTZCQ5J4q4vyzYuNCWQ7ydB ABVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:mime-version:to:from:subject:date :importance; bh=WwOsRp5BzU0pXPqzjO9ez2yyAnUXX2mEX82eeUxMu0A=; b=d41V6qRsKRRA4QboDgHD60hQ5Fyp+K/SjjTOg1a/ZDn60yRWZtBwkaP18bHFRnxnEX BYmbrFrp1WvVp9kCwBu4WW6wWCGCrswdJ4awLoVmdGpgc8SiUDLQ3AUb/ljb5o2w9HeZ pZlnqydD7ReULRwFZ/2y4KzrQ1BLibDirzGOf1Bt10VmT17xdCU0So8GQGKGuW+xyjdE 9rWn0kVFG6jJRotKU4XZxkpJPy220aNHcb+x5KWhQJSb4ZRSEFYu6IMxhorlECxyXMgu hwaPnQOroRBbW9MpurosSR9Z8D817Vj9hrKUh9XJGlsa43E9VzByGfkua0b2TsKXDoAg k4Nw== X-Gm-Message-State: ABuFfohinWO3P+W97qSgBrcG2FL9jqXtZvLQsaOL96f4vGzVXppZgEJc E899sYPDL57iwu4zzO2ZYhezyPU9YJ/mIA== X-Google-Smtp-Source: ACcGV63skesA+LA2/7QTkbhQIaIa4H2lePGOsthC52YsNeBK99L7xWOr9+LVkaUHXwqnnScumFOUvA== X-Received: by 2002:a63:e04d:: with SMTP id n13-v6mr15676329pgj.426.1540000748981; Fri, 19 Oct 2018 18:59:08 -0700 (PDT) Received: from ?IPv6:2001:da8:200:9002:bdf3:c3e0:61f1:7dd2? ([2001:da8:200:9002:bdf3:c3e0:61f1:7dd2]) by smtp.gmail.com with ESMTPSA id q25-v6sm39000084pfk.154.2018.10.19.18.59.07 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Oct 2018 18:59:08 -0700 (PDT) Message-ID: <5bca8bec.1c69fb81.81f91.2e08@mx.google.com> MIME-Version: 1.0 To: "users@dpdk.org" From: Xiao Kong Date: Sat, 20 Oct 2018 09:59:08 +0800 Importance: normal X-Priority: 3 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] RSS problems with Intel XL710 NIC (i40e) X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Oct 2018 01:59:10 -0000 Dear all, We are currently trying to build a multi-RX-queue dpdk program, using RSS t= o split the incoming traffic evenly into RX queues on a single port. It wor= ks fine when we use an Intel 82599ES 10Gig NIC. However when we switch to t= he Intel XL710 40Gig NIC (i40e), RSS does not seem to work. As a result, TC= P packets belonging to various flows (with different src&dst IPs, ports) ar= e all sent into the same RX queue. Below is our code. static const struct rte_eth_conf port_conf_default =3D { =C2=A0=C2=A0=C2=A0 .rxmode =3D { =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 .max_rx_pkt_len =3D ETHER_MAX_LE= N, //1518 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 .mq_mode =3D ETH_MQ_RX_RSS, =C2=A0=C2=A0=C2=A0 }, =C2=A0=C2=A0=C2=A0 .rx_adv_conf =3D { =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 .rss_conf =3D { =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 .rss_key= =3D NULL, =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 .rss_hf = =3D ETH_RSS_IP | ETH_RSS_UDP | ETH_RSS_TCP | ETH_RSS_SCTP, =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 } =C2=A0=C2=A0=C2=A0 }, }; We noticed that it is mentioned on several pages that XL710 sometimes behav= es quite differently from other NICs, but we just can't find a way to confi= gurate RSS hash fields on our card. Another thing is when we tried to enabl= e RSS or setup hash fields in testpmd, it showed error messages as follows. testpmd> port config all rss all=20 Configuration of RSS hash at ethernet port 0 failed with error (22): Invali= d argument. Configuration of RSS hash at ethernet port 1 failed with error (22): Invali= d argument. testpmd> show port 1 rss-hash ipv4 RSS disabled I am wondering if there is any mistake we made or if there is a unique meth= od for XL710 to configure RSS hash fields. By the way, we are using DPDK ver. 17.08. Thanks.=C2=A0=20 -------------------------- Best Regards, Kong