From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0EE82A0471 for ; Sat, 17 Aug 2019 09:43:26 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id F07FB343C; Sat, 17 Aug 2019 09:43:24 +0200 (CEST) Received: from mail-vs1-f47.google.com (mail-vs1-f47.google.com [209.85.217.47]) by dpdk.org (Postfix) with ESMTP id C1FA1374 for ; Sat, 17 Aug 2019 09:43:23 +0200 (CEST) Received: by mail-vs1-f47.google.com with SMTP id i128so5176625vsc.7 for ; Sat, 17 Aug 2019 00:43:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8HlECv64HYD7lWG92ZIRZwogf1RPYKmv8bAVX8AL5Qo=; b=HIy8WpBOnh+KWmvh400WcsCeg8IsgfGdpUxOOMcvpwOsu0I07ASA+dSkt8s69mO6JC EWHadWAmjYtLPsBENVzJgMnlA20IQ0m4LRgrB93EYpxU/Puz84Z1Mq8TRQa4+cqhJ1aN iZxzB6bqQu3vMyDU224lZT6VjnWeFW0gV9f/AYHHdwnDj1SLqAwlYKw7VHATjFJ4NrI3 lU3CblDp7iyAEkE+UBTBpEfNJq5xFnz5NEfYxxxq5XL7Kixl+eGDfau0B02Ok/0JaT3V 7fOAOqGUC3Segj6UIjqxkq4sJp8itCHSLU6QWQo7hzFj7BIepGlVUciU2KpTvXjxEc6w adtA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8HlECv64HYD7lWG92ZIRZwogf1RPYKmv8bAVX8AL5Qo=; b=Bw9YWyPf4Kjbg1rkVH9AFMJQjzpitEHorFFIcfu0qMVL79rCx7+X5m7WTk+CuHDg9h KkLASZ+6+wdLNNCg6h2nMYTBYSJ6JM025lUT0x/C7aIgKWYOAbUjYMV7I6WbT5mPqM1U GhJl0NXyVhpKUdYSjSczaB4JPzDc03s9uykHW2XwrxlAePSi6yRP/cdUmTvCPUpn64/F g5wETyIX1QYkIr/TDfq8QRBjylxlfeJdGvkmEdGjciuy20Jjp/Hzg+wm4ltay2HM6pP2 97fXs25PEp3gLP4Tw3IcYj7V+sdCLyWR0Y4OC61uFjg9LU1Cr3L4f+vNFjlY/2xZCdmy 9pPA== X-Gm-Message-State: APjAAAUVVosiE68bWkNGPepjkdiGdvtcfhsCoTWjnWA3XTEHGeHGNsw6 ClLt3JfeLhYgJ4EUkDGsUwr9OqZJeXsEwaJVqLzozA== X-Google-Smtp-Source: APXvYqwTTBx99OGyKaRZg3RjfnvElNG7eFDNqoBYZJIeoVl+JDC4WEL4UuzsbCMESp4NVlYlNStHV1ThO46o0mmsg5o= X-Received: by 2002:a67:1787:: with SMTP id 129mr8348408vsx.64.1566027803090; Sat, 17 Aug 2019 00:43:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Victor Huertas Date: Sat, 17 Aug 2019 09:43:11 +0200 Message-ID: To: dev@dpdk.org Cc: Vikutoru Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] DPDK (v17.11) ACL table field format definition enhancement: 'offset' field covering headroom space. X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi all, I am developing an application with DPDK (v17.11) using a concatenation of pipelines. Now I find myself on the definition of an ACL table and more precisely the format of the ACL fields. One of the parameters of this field format is the 'offset', which indicates the number of bytes till the start of the field to check. All the examples I have seen so far assume that an offset value of 0 means the start of Ethernet header and not the start of rte_mbuf struct. Is there a way to place the offset start at the rte_mbuf struct? If not, I think that it would be a useful enhancement. That's why I propose it in the developers mailing list. What do you think about this? Thanks a lot for your attention. -- Victor -- Victor