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 5B47245847; Thu, 22 Aug 2024 17:16:06 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1E39442EE3; Thu, 22 Aug 2024 17:16:06 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id A954542E52 for ; Thu, 22 Aug 2024 17:16:04 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1724339764; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bdH9pidj09IxCFnjtGJb6KWhrxoSxcdNAfDPHqw2ZCg=; b=ILY0fkTDg1xJQ6G0/sLPGDgh3j0LwhfG0TGKCn00POplR4Zmbcq8gBJ2mPPvS51CCQysxK ddE3h3TM9Xp1+A1gSEeIwfXxbHqvfoQTpVg3GZ3cQagC/icaXYTqcPW0sw4x/nb0EoPHHI 8nVtT4f+W7sgPImRgBg1iKm6BNIK/RQ= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-354-hfScUCICPueIPeKuogSGdg-1; Thu, 22 Aug 2024 11:16:03 -0400 X-MC-Unique: hfScUCICPueIPeKuogSGdg-1 Received: by mail-wr1-f69.google.com with SMTP id ffacd0b85a97d-3718d9d9267so474230f8f.0 for ; Thu, 22 Aug 2024 08:16:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724339762; x=1724944562; h=in-reply-to:references:user-agent:to:from:cc:subject:message-id :date:content-transfer-encoding:mime-version:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=bdH9pidj09IxCFnjtGJb6KWhrxoSxcdNAfDPHqw2ZCg=; b=EL6xShqJNqDR0P89S31Y+66MsXyfrzumb/tLmRSMcGpCPPfRp2m13nVdqQg444BVgb FXSKltofD+2r+umlCBaLY4vJnYRpMD62yWIIDyl0UKbjTEVJAiaf8gZhud8QMj8VahhH yzEXi9JsLemIbxGHvLxMbf9Hc+bYvSfRPLBHt6iqYQKXghAwgbDN+fiMqT2+8QPEyN5X xOjsx2x9enGnyWGIzP2V4fP+OspcE0dXGOoqHBwAxFTOplvaroHPgiiiEPkPC9h1knAl fbzKCOuiShPKrCLjD2poddjHTIVvWDVKQQG2z9ymg1SyJU4Lg0C5ZNdVjwqZfcoFLGLq /o5Q== X-Gm-Message-State: AOJu0Yz6cyPoi52HvcraeZH07/7vpSTiip+pXkED3EWkXP9IakCkX1EW v0jkEnYGY842qthaboE9Kre+Gi1AiF7SJBJrYYuJKwZ3/O9mXlXTjwFVbgCiJ18hNHPHI44Do3d mYC83EF+oD36Zzp+vxPZMx6BSlLB3wGX7nfyuxhQC X-Received: by 2002:adf:ee49:0:b0:368:37ac:3f95 with SMTP id ffacd0b85a97d-372fd5aaf0dmr3412987f8f.31.1724339761852; Thu, 22 Aug 2024 08:16:01 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGemyg2XvRXZjMJ4D52z8Io/BWwvFRcG5FiZCFpKAqFqwRH9+sAbzc4YT/WR2asSgP++fTQ+w== X-Received: by 2002:adf:ee49:0:b0:368:37ac:3f95 with SMTP id ffacd0b85a97d-372fd5aaf0dmr3412962f8f.31.1724339761336; Thu, 22 Aug 2024 08:16:01 -0700 (PDT) Received: from localhost (2a01cb00025433006239e1f47a0b2371.ipv6.abo.wanadoo.fr. [2a01:cb00:254:3300:6239:e1f4:7a0b:2371]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-42ac514e07csm28090145e9.10.2024.08.22.08.16.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 22 Aug 2024 08:16:00 -0700 (PDT) Mime-Version: 1.0 Date: Thu, 22 Aug 2024 17:16:00 +0200 Message-Id: Subject: Re: [PATCH dpdk v1 00/15] IPv6 APIs overhaul Cc: , =?utf-8?q?Morten_Br=C3=B8rup?= , "Vladimir Medvedkin" , "Konstantin Ananyev" , "Bruce Richardson" From: "Robin Jarry" To: "Stephen Hemminger" User-Agent: aerc/0.18.2-53-g11f57b5f3378-dirty References: <20240821162516.610624-17-rjarry@redhat.com> <20240822071352.5e4766ba@hermes.local> In-Reply-To: <20240822071352.5e4766ba@hermes.local> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8; format=Flowed 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 Stephen Hemminger, Aug 22, 2024 at 16:13: > Why does DPDK need to have its own definitions of IPv4 and IPv6 addresses= ? > The structures in_addr and in6_addr exist on Linux, BSD, and Windows. > It creates lots of code reimplementation (see inet_ntop etc). By the way, you can call inet_ntop(AF_INET6) with the rte_ipv6_addr type=20 I introduce here. It works fine.