From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id EC32445847; Thu, 22 Aug 2024 17:14:14 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DF04142EE7; Thu, 22 Aug 2024 17:14:14 +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 0F9C44027A for <dev@dpdk.org>; Thu, 22 Aug 2024 17:14:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1724339652; 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=2c7tAToul3z/XA405STTpMpaiAXzZFh/SF+t2D7xEik=; b=YmXRLMZAD8lJYtaQJ39cJwT3E29dkn9TmHGkfVDH9myVRuMkPhiBIW8pWNLay31j2Y/5LA VqKVC6G3UMv49EJ4yVT/CrRU2qc79G8EzcFx/ZwOELirApMRV1OKRGkpkRjPn3++IxuWmO 9Xwq+mYzzld+xMlvyzGFY8t5j9Q+an0= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-282-kLkXVvJ_PAm2CZfMkT1h5A-1; Thu, 22 Aug 2024 11:14:11 -0400 X-MC-Unique: kLkXVvJ_PAm2CZfMkT1h5A-1 Received: by mail-wm1-f69.google.com with SMTP id 5b1f17b1804b1-429e937ed39so8661555e9.1 for <dev@dpdk.org>; Thu, 22 Aug 2024 08:14:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724339650; x=1724944450; 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=2c7tAToul3z/XA405STTpMpaiAXzZFh/SF+t2D7xEik=; b=VVOwrl8lWtutwCZ6QSCD68SSf2E/4ZWeMsNRz2xuAjSSBCxcxj+4dLCPGdd4Dc8lgm km3u2t6guuRrRjWJ6v6C4bP9QZGRFJNATJ2HJ9umawpaRco1HyRNmHatKBd77UUEit5D LClJAs9vPUj1i6QUdzBQhJPv/PDblWFqCMRkTBBNGt12xuXCWbSBl/UHPUmSV5keu+s0 5/+QEtDPfEhBG03nOh+bQlWmyjv0/9TCYM7OX9MUHZjmIFxA0pDcZkqZ3AlsCrDBOjX/ 2h+NqhDMrVI38rKadeR+ap51Z/S20vIukA3wlDe8IC1sUtcHZ+rZ4lsDsWoKRIobj5Le IjtQ== X-Gm-Message-State: AOJu0YzY1dPuDYcReOaX+QhJgx2RE8SlBGOQlfkAjo1UlgvlJQHBuWeY I86e93EgpK1KvKa2B2Obwdnw+jp3Ou+7ZoZV25b+Mw/iHcK6m9JkpanIVGURzrb24ooCYQf1y8V f5Ay5xlN6CPAhQjQe5X5Ahan/8AqEwCFxDXo1oN+H X-Received: by 2002:a5d:6182:0:b0:362:7c2e:e9f7 with SMTP id ffacd0b85a97d-372fd5aa50bmr3823864f8f.32.1724339650107; Thu, 22 Aug 2024 08:14:10 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHyQKfNMxXyYVON/cD9awOX5JP/SldH+Au3VN/OzB4xWQUOW5CLy5bK4pz+bZ9q3vm0g6dvPQ== X-Received: by 2002:a5d:6182:0:b0:362:7c2e:e9f7 with SMTP id ffacd0b85a97d-372fd5aa50bmr3823827f8f.32.1724339649533; Thu, 22 Aug 2024 08:14:09 -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-42ac514e1f7sm27438335e9.5.2024.08.22.08.14.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 22 Aug 2024 08:14:09 -0700 (PDT) Mime-Version: 1.0 Date: Thu, 22 Aug 2024 17:14:08 +0200 Message-Id: <D3MJE2V8ZVGJ.LEN1V8ZMK2JG@redhat.com> Subject: Re: [PATCH dpdk v1 00/15] IPv6 APIs overhaul Cc: <dev@dpdk.org>, =?utf-8?q?Morten_Br=C3=B8rup?= <mb@smartsharesystems.com>, "Vladimir Medvedkin" <vladimir.medvedkin@intel.com>, "Konstantin Ananyev" <konstantin.ananyev@huawei.com>, "Bruce Richardson" <bruce.richardson@intel.com> From: "Robin Jarry" <rjarry@redhat.com> To: "Stephen Hemminger" <stephen@networkplumber.org> 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 <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Stephen Hemminger, Aug 22, 2024 at 16:13: > Let me ask a couple of questions about this. > > 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). > > What advantage is there to having our own definitions? If I'm not mistaken, in6_addr is aligned on 4 bytes. Is it guaranteed=20 that IPv6 headers will *always* be starting on a 4 bytes boundary? If=20 not then, in6_addr cannot be mapped on unaligned packet memory.