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 3E1AD43B4E; Mon, 19 Feb 2024 20:50:23 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B8D7940275; Mon, 19 Feb 2024 20:50:22 +0100 (CET) Received: from mail-pf1-f170.google.com (mail-pf1-f170.google.com [209.85.210.170]) by mails.dpdk.org (Postfix) with ESMTP id 84A2D40263 for ; Mon, 19 Feb 2024 20:50:21 +0100 (CET) Received: by mail-pf1-f170.google.com with SMTP id d2e1a72fcca58-6e46e07ff07so552895b3a.3 for ; Mon, 19 Feb 2024 11:50:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1708372220; x=1708977020; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=JFsxJOVjq2MBU7IQN4gkkg8JsxRbbs2JKLVNgz6TZjw=; b=1gsqNueU9qo+B5kOZAz9AoSrDr1uqlR88DKvGecGtHaqrDSvqduZmwJO/5NtyLuOCr G2qjFSY71o3M7POBycb+zdVnQ6Et5ZiYd/ozrOqKeybZbL2S9gBUixciAdaIb4Xf9OH/ ngBNDefy9qXy4DIgk/8oEgQfNvLIWak58W7FpaTvUp74ISx2Ts+HVto3qG44J1uQduRR PX2K1OfNAr88RxD4IqXvxl+Mez24ick4yHdg94D+4gQXAwpkgYrMyei/3EYesiTb+Kuc 38yHDbCdgM8C0TWuccltxEHoqdzdN5wOycL9QNQ235CQGnmph7hsQGC4fYPpFLyCuQxK t6RQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708372220; x=1708977020; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=JFsxJOVjq2MBU7IQN4gkkg8JsxRbbs2JKLVNgz6TZjw=; b=kGO+1zbbAq1pAg3HkLZON46A+HCqTkOhRRUnHtzWhyXXG2TVRttFKrU7P45AfIQfUC 5O/LLyMcK1EAHSdrrwp5LWCBcS0NcWPR+qBxCasqdfVsNfBvUJIkp/fqE4ZlooeztVWJ Nr5jvaaDaPCjL/tK2gta4C/4cCSMXgKgGZdKKTmKB+G6fSWk2hxZu7vjx39ya+Gxr64u hpCcdQE1dgdjmj9Okyl/vyNCzBzKrwP/9kqwSMSjxzq05Efa+pxc99+QcxkpTz0lCMgY 0x3c/3fwMD3EmA06TuAcG2jk2QQX6HSCY8NFH5P7VsDeWobv3dHkL+84pc3ixJz3qaQP m4SQ== X-Gm-Message-State: AOJu0Yzr7QpUmv3usm8wXF1RMvzO7Lh2BcrF8T4PCCjfyhz0ptlm5zch C/s/KOappkny6KGCa+2ZFvByUvBo3LZe+yYHrwpB5ZhUfak0JD1ZKj015D05KQU= X-Google-Smtp-Source: AGHT+IFW3wJFaCt4fH+bG+icHFhi3duTcc19c8y5AsVyxHUCVfxizjuzcFFdbUYyHpE27kJomLyYRQ== X-Received: by 2002:a05:6a00:139d:b0:6e0:f752:b442 with SMTP id t29-20020a056a00139d00b006e0f752b442mr16178692pfg.7.1708372220461; Mon, 19 Feb 2024 11:50:20 -0800 (PST) Received: from hermes.local (204-195-123-141.wavecable.com. [204.195.123.141]) by smtp.gmail.com with ESMTPSA id g29-20020a63521d000000b005dc491ccdcesm4362717pgb.14.2024.02.19.11.50.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 19 Feb 2024 11:50:20 -0800 (PST) Date: Mon, 19 Feb 2024 11:50:17 -0800 From: Stephen Hemminger To: Gavin Li Cc: , , , , , , , , , , Subject: Re: [V1 0/5] support VXLAN-GPE header fields(flags, rsvd0 and rsvd1) matching Message-ID: <20240219115017.02497c80@hermes.local> In-Reply-To: <20240112080210.1288356-1-gavinl@nvidia.com> References: <20240112080210.1288356-1-gavinl@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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 Fri, 12 Jan 2024 10:02:05 +0200 Gavin Li wrote: > Previously, VXLAN-GPE in DPDK only supports VNI and next protocol header > fields. This patch series add support for flags and reserved field 0 and > 1. > > Below is the VXLAN-GPE header defined in the lasted draft. > 0 1 2 3 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > |R|R|Ver|I|P|B|O| Reserved |Next Protocol | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | VXLAN Network Identifier (VNI) | Reserved | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Would recommend against implementing anything in a draft RFC. Things can change. Learned the hard way when doing VXLAN driver for Linux. The hardcoded port value in the Linux VXLAN driver is wrong because it matched the draft RFC (got changed in final version). Because of strict compatibility requirements the Linux driver could not be changed to the correct value.