DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Shijith Thotton <sthotton@marvell.com>
Cc: jerinj@marvell.com, bruce.richardson@intel.com,
	pbhagavatula@marvell.com,  dev@dpdk.org,
	Wathsala Vithanage <wathsala.vithanage@arm.com>,
	 Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	 Sunil Kumar Kori <skori@marvell.com>,
	Satha Rao <skoteshwar@marvell.com>,
	 Harman Kalra <hkalra@marvell.com>
Subject: Re: [PATCH v4] common/cnxk: allow enabling IOVA field in mbuf
Date: Wed, 30 Oct 2024 15:59:18 +0530	[thread overview]
Message-ID: <CALBAE1NXS5n5BYKsJcFnJDqPUgzjwc6aZ8kF0GBH_aUyU_4MSQ@mail.gmail.com> (raw)
In-Reply-To: <20241028094310.2412436-1-sthotton@marvell.com>

On Mon, Oct 28, 2024 at 3:13 PM Shijith Thotton <sthotton@marvell.com> wrote:
>
> The value of RTE_IOVA_IN_MBUF has always been disabled on CNXK
> platforms, as IOVA in the mbuf is unnecessary. This update changes that
> behavior to respect the value set by the user. A warning message will be
> printed if the build is configured to enable IOVA on the CNXK platform.
>
> Signed-off-by: Shijith Thotton <sthotton@marvell.com>

Applied to dpdk-next-net-mrvl/for-main. Thanks

      reply	other threads:[~2024-10-30 10:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 11:06 [PATCH] " Shijith Thotton
2024-10-24 11:10 ` Jerin Jacob
2024-10-24 12:09   ` Bruce Richardson
2024-10-24 16:13     ` [EXTERNAL] " Shijith Thotton
2024-10-24 16:44       ` Bruce Richardson
2024-10-25  9:41         ` Shijith Thotton
2024-10-25  9:50 ` [PATCH v2] " Shijith Thotton
2024-10-25 10:06   ` Bruce Richardson
2024-10-25 10:12     ` Shijith Thotton
2024-10-25 11:51   ` [PATCH v3] " Shijith Thotton
2024-10-25 12:39     ` Bruce Richardson
2024-10-28  9:43     ` [PATCH v4] " Shijith Thotton
2024-10-30 10:29       ` Jerin Jacob [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALBAE1NXS5n5BYKsJcFnJDqPUgzjwc6aZ8kF0GBH_aUyU_4MSQ@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=hkalra@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=sthotton@marvell.com \
    --cc=wathsala.vithanage@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).