From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from gandalf.ozlabs.org (gandalf.ozlabs.org [150.107.74.76]) by passt.top (Postfix) with ESMTPS id 0DE0D5A0278 for ; Wed, 28 Feb 2024 12:25:32 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gibson.dropbear.id.au; s=202312; t=1709119522; bh=YSMATV+VwQtZdrxbhUo/sSP6jSeZL+qeSHkOSQcCvtI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=KQZQfcuJchk7007Bj6r0UqIDRxwkakrTlJuxW3/kGdzMV//lPWen74IHfKyaEizNb ksnFKLYxW23zPO1bM0onN95GVJ8EXx4mgHTrj/3ULIsbrB+aiDje0tijF2uaFwxb9z 4yMpYwRson0uyiyR4Prp/szojSk1ErL3a63BMqts8Ei8r12+WvbsICLMbC2OBlLBOr YbwKf9om5X8vjFTw3kkgHX4vs+edTCtN80xjHLnGPIsCnTgKMsMepR3l7TC3vyIlH1 Zbkb8cex9h4e5MkO0udKvWqQeYukYx68m49xqilMrkAmF0Es1KwM8THVrkNKM9Zhv1 kxw5Ex8EBqaSw== Received: by gandalf.ozlabs.org (Postfix, from userid 1007) id 4TlBq65FHMz4wxx; Wed, 28 Feb 2024 22:25:22 +1100 (AEDT) From: David Gibson To: passt-dev@passt.top, Stefano Brivio Subject: [PATCH v3 07/20] flow: Add helper to determine a flow's protocol Date: Wed, 28 Feb 2024 22:25:07 +1100 Message-ID: <20240228112520.2078220-8-david@gibson.dropbear.id.au> X-Mailer: git-send-email 2.43.2 In-Reply-To: <20240228112520.2078220-1-david@gibson.dropbear.id.au> References: <20240228112520.2078220-1-david@gibson.dropbear.id.au> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID-Hash: G5YWUGU6NLUVHPWOEUVHN2EEGSCP67PT X-Message-ID-Hash: G5YWUGU6NLUVHPWOEUVHN2EEGSCP67PT X-MailFrom: dgibson@gandalf.ozlabs.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: David Gibson X-Mailman-Version: 3.3.8 Precedence: list List-Id: Development discussion and patches for passt Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Each flow already has a type field. This implies the protocol the flow represents, but also has more information: we have two ways to represent TCP flows, "tap" and "spliced". In order to generalise some of the flow mechanics, we'll need to determine a flow's protocol in terms of the IP (L4) protocol number. Introduce a constant table and helper macro to derive this from the flow type. Signed-off-by: David Gibson --- flow.c | 7 +++++++ flow.h | 4 ++++ 2 files changed, 11 insertions(+) diff --git a/flow.c b/flow.c index 5e94a7a9..beb9749c 100644 --- a/flow.c +++ b/flow.c @@ -25,6 +25,13 @@ const char *flow_type_str[] = { static_assert(ARRAY_SIZE(flow_type_str) == FLOW_NUM_TYPES, "flow_type_str[] doesn't match enum flow_type"); +const uint8_t flow_proto[] = { + [FLOW_TCP] = IPPROTO_TCP, + [FLOW_TCP_SPLICE] = IPPROTO_TCP, +}; +static_assert(ARRAY_SIZE(flow_proto) == FLOW_NUM_TYPES, + "flow_proto[] doesn't match enum flow_type"); + /* Global Flow Table */ /** diff --git a/flow.h b/flow.h index 48a0ab4b..e9b3ce3e 100644 --- a/flow.h +++ b/flow.h @@ -27,6 +27,10 @@ extern const char *flow_type_str[]; #define FLOW_TYPE(f) \ ((f)->type < FLOW_NUM_TYPES ? flow_type_str[(f)->type] : "?") +extern const uint8_t flow_proto[]; +#define FLOW_PROTO(f) \ + ((f)->type < FLOW_NUM_TYPES ? flow_proto[(f)->type] : 0) + /** * struct flow_common - Common fields for packet flows * @type: Type of packet flow -- 2.43.2