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 DBE7643D48; Mon, 25 Mar 2024 18:20:34 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id ABB8640695; Mon, 25 Mar 2024 18:20:34 +0100 (CET) Received: from mail-pj1-f52.google.com (mail-pj1-f52.google.com [209.85.216.52]) by mails.dpdk.org (Postfix) with ESMTP id 3A58C40298 for ; Mon, 25 Mar 2024 18:20:33 +0100 (CET) Received: by mail-pj1-f52.google.com with SMTP id 98e67ed59e1d1-2a072747fc6so591413a91.2 for ; Mon, 25 Mar 2024 10:20:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1711387232; x=1711992032; 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=ch//DzHPeFykAW3/z6biJPGJWePxyao4wZwlx81IljI=; b=HO6WjJNdByKNMbdST+NL5ylHtZ1aUiQlD+ApDyaIgZ8l7xI8EBmEDI1ndSgZdO65li eEvBaeOMMZ1kyhtNbdmt4uE95fmB9m4GjbEe9Df/vZjsowukSFe1MSw5eBzh0kw7HLcT eMHxS1R8F2+etWoT0fKfMlXrSOF0uXigHNYNN+d4GAWY3c3ojWlFTi1Gn8VMRsNp5aL9 BWta5CU4zzieDD9w+KkUoXfTSFN7gFXGg4kixcP/L7Q6/BuwpD9LKxH9+N1JiMOhYrWM L+u8ZCs+wzf+DqndpRngRDvgS0VzSIwAN6R4912AchjMFnXJcBopGbQwUUhq2GtUDWTC 6bmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711387232; x=1711992032; 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=ch//DzHPeFykAW3/z6biJPGJWePxyao4wZwlx81IljI=; b=QX9Snrj5KQn8COm+kzGgHuGd+DJ5rBLBzFuIGUP0AIBKWHIHjgHzLcruFypzLKsEUa TGHcnIQ64ZPSJbuG1Sgv63+F7qSb/3JTN0SqkeDHuLw9URZOeGdQTbJ7yWeh008/oNP/ hY29lzXu91hTRipGiTnuaZPTy1OWsD3mLJOqR8SrXwX2r7fSe8/bjbL5dZ6q8NWQa9sr URT1qpDHf2KG6APepLrKnwYaZKciykRJ4qgPYvBHRuvB1NP6CKoKCJ+HcarThVZ649YT W8C1a4nxdNFGV3f4BUFCLKaKsX0nrFvVErxGs4+6Az7nNfLF7r2GckRfZuKn6S7E3l9b iNfQ== X-Forwarded-Encrypted: i=1; AJvYcCUNcygdvzM6DYHI289VJJyCsDcuN8LSDkch4j+RutTNID7dRhUDgW51NHhDUuaEgNmFfKGYTEwZ/7BYyjY= X-Gm-Message-State: AOJu0YwdFwiBL95vQxoJM/5x6IEzIIOU0JPp2zQzKH6JQY6+VrFwmSGj s9h9wKZxop3GLdym2X9j8CEDzjPaAcEu/wkqXfbR4sU5yfsQnW51bBKHJ1BzmTk= X-Google-Smtp-Source: AGHT+IESGrKt8pQNkdK/ttjO5VN3bnYsy3HREsOJ2YH7wrq3tmOQKeTOuqRxNfc1MTEm6iHUmJV8YQ== X-Received: by 2002:a17:90b:fc6:b0:2a0:2a93:d8d8 with SMTP id gd6-20020a17090b0fc600b002a02a93d8d8mr4944028pjb.41.1711387232329; Mon, 25 Mar 2024 10:20:32 -0700 (PDT) Received: from hermes.local (204-195-123-203.wavecable.com. [204.195.123.203]) by smtp.gmail.com with ESMTPSA id d60-20020a17090a6f4200b002961a383303sm11299829pjk.14.2024.03.25.10.20.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 25 Mar 2024 10:20:32 -0700 (PDT) Date: Mon, 25 Mar 2024 10:20:30 -0700 From: Stephen Hemminger To: Bruce Richardson Cc: Garrett D'Amore , "dev@dpdk.org" , Parthakumar Roy Subject: Re: meson option to customize RTE_PKTMBUF_HEADROOM patch Message-ID: <20240325102030.46913a06@hermes.local> In-Reply-To: References: 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 Mon, 25 Mar 2024 10:01:52 +0000 Bruce Richardson wrote: > On Sat, Mar 23, 2024 at 01:51:25PM -0700, Garrett D'Amore wrote: > > So we right now (at WEKA) have a somewhat older version of DPDK that we > > have customized heavily, and I am going to to need to to make the > > headroom *dynamic* (passed in at run time, and per port.) > > We have this requirement because we need payload to be at a specific > > offset, but have to deal with different header lengths for IPv4 and now > > IPv6. > > My reason for pointing this out, is that I would dearly like if we > > could collaborate on this -- this change is going to touch pretty much > > every PMD (we don't need it on all of them as we only support a subset > > of PMDs, but its still a significant set.) > > I'm not sure if anyone else has considered such a need -- this > > particular message caught my eye as I'm looking specifically in this > > area right now. > > > Hi > > thanks for reaching out. Can you clarify a little more as to the need for > this requirement? Can you not just set the headroom value to the max needed > value for any port and use that? Is there an issue with having blank space > at the start of a buffer? > > Thanks, > /Bruce If you have to make such a deep change across all PMD's then maybe it is not the best solution. What about being able to do some form of buffer chaining or pullup.