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 F37FC4260C for ; Tue, 19 Sep 2023 18:30:26 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E8B7D40EDB; Tue, 19 Sep 2023 18:30:26 +0200 (CEST) Received: from mail-ua1-f50.google.com (mail-ua1-f50.google.com [209.85.222.50]) by mails.dpdk.org (Postfix) with ESMTP id EFEF340277; Tue, 19 Sep 2023 18:30:23 +0200 (CEST) Received: by mail-ua1-f50.google.com with SMTP id a1e0cc1a2514c-7a512434bc9so4474269241.0; Tue, 19 Sep 2023 09:30:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695141023; x=1695745823; darn=dpdk.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=R38vZDWJzKUoMY8Z6BSQly4wmWX/fASlMHTzcD8PkV4=; b=cgAlpik84+K8X4PulaiuiMBTc37MUGVf5L3CQNJ4xiHL42Y5i8HCqdDvfb6FjOcqnR SocdaOWTRQwhL3dgZGxkOMVzxhHYtOuj0eu2lnwkTB/mSL9M1KfUlh8rXpVsFOkxj7QF IlApk1R5/eTJT0Y0c6PCcAAC386WsNFaSGc/MCmyGbepyPINFKSfCxjwor7+NZhhYkgL yc145lYbI0DzDE8A+tZHQMvCNWrD8V4oa8+ugu2w8JJI7dzYqdHtxte43s9AydqyJVf8 ipnP5ajT4WezmWLPfdiw3NvOlFMW5bZzwxWn6lWS9LjWf95ZNT0stywaIwXzL0HGg/lw T9eA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695141023; x=1695745823; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=R38vZDWJzKUoMY8Z6BSQly4wmWX/fASlMHTzcD8PkV4=; b=GSwXPzdG2xcdlS9nyrv8YSmpi6VY2kiE+BCyFzueq6knihqzSLsgG7efaoSfzkMcN3 l5taN0DGyzkp+otbSfcPQKVLEFrYISxeYzg6MATaNh97f5/S7ipmkQ0YXa5Uvu/9Wckr 4aS14PiaHbsY9GSKsuvpsfMCeW+3LjjMB7s2LrfvBEEfP0yRur0SDSzTgRcoYAKhL+s+ viCpKUDpo/xt7dxdZ7Nrl1hPUe+SoQIpLSVdiPcv/gwdrUoG0FfbglNcS5n2MiqrYJs/ WWtWZbiitIRE5u4A2yRuRVzZ218LyX9VKdJ6IyZmbgNvkFOJcw1xrgj74mOlTwUqVhWw N1aw== X-Gm-Message-State: AOJu0Yw+EOss1AZ+UyEObi/TqE/NViqGf6PEcXwNMn+B/7f5fMpvlUUN ZKXeO2uyANfXk+cYr3o9BSj0jP8ki4j7qpJk77g= X-Google-Smtp-Source: AGHT+IEGa+n3JotdsVQ1e9Sjl4VbtAc9ixAvE+MwAGGoXy7FScrjugfcu6+80tqFEP+1HI2V967v9ky2RHJXQwW5Cik= X-Received: by 2002:a67:bc06:0:b0:452:69f8:a00d with SMTP id t6-20020a67bc06000000b0045269f8a00dmr208346vsn.2.1695141023142; Tue, 19 Sep 2023 09:30:23 -0700 (PDT) MIME-Version: 1.0 References: <20230918082553.704859-1-rbhansali@marvell.com> In-Reply-To: <20230918082553.704859-1-rbhansali@marvell.com> From: Jerin Jacob Date: Tue, 19 Sep 2023 21:59:57 +0530 Message-ID: Subject: Re: [PATCH] eventdev/eth_rx: fix timestamp field register in mbuf To: Rahul Bhansali Cc: dev@dpdk.org, Naga Harish K S V , Jerin Jacob , Ganapati Kundapura , stable@dpdk.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org On Mon, Sep 18, 2023 at 6:46=E2=80=AFPM Rahul Bhansali wrote: > > For eventdev internal port, timestamp dynamic field registration > in mbuf is not required as that will be done from net device. > For SW eventdev, Rx timestamp field registration will be > done during Rx queue add operation as per device capabilities and > offload configuration. > > Fixes: 83ab470d1259 ("eventdev/eth_rx: use timestamp as dynamic mbuf fiel= d") > Cc: stable@dpdk.org > > Signed-off-by: Rahul Bhansali Ping for review from maintainer.