From: Bhagyada Modali <bhagyada.modali@amd.com>
To: David Marchand <david.marchand@redhat.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Jingjing Wu" <jingjing.wu@intel.com>
Cc: <dev@dpdk.org>, Selwin Sebastian <Selwin.Sebastian@amd.com>,
"Raghavendra Ningoji" <raghavendra.ningoji@amd.com>,
Robin Jarry <rjarry@redhat.com>,
Sachin Saxena <sachin.saxena@oss.nxp.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [v1,0/3] raw/ntb: add AMD NTB support
Date: Fri, 25 Sep 2026 14:47:21 +0530 [thread overview]
Message-ID: <20260925091721.2234369-1-bhagyada.modali@amd.com> (raw)
In-Reply-To: <CAJFAV8wJKYoid=NnVkT81K0A-3v160xvrsstDj8bhAKaK3Ankg@mail.gmail.com>
On Thu, Sep 18, 2026 at 03:06:49PM +0000, Bruce Richardson wrote:
> > + void (*interrupt_handler)(void *param);
> > + /* Optional vendor-specific handshake. If NULL, the built-in
> > + * scratchpad handshake is used. Used by hardware (e.g. AMD) whose
> > + * scratchpad layout differs from the built-in protocol.
> > + */
> > + int (*dev_handshake)(const struct rte_rawdev *dev);
> > + /* Optional vendor-specific peer-config read at device start. If NULL,
> > + * the built-in scratchpad reads are used.
> > + */
> > + int (*read_peer_config)(const struct rte_rawdev *dev);
> > };
>
> For these new op fields, do you foresee cases where other drivers might use
> the "default" functions as you have now? Might it be better to simplify
> things and always use driver-supplied ops, converting the existing
> functions into intel-specific ops, rather than making them fallback
> functions?
Hello David, Jingjing, Bruce,
We are close to the RC1 window and have not yet received any review feedback.
We are hoping to have the series considered for RC2 and would appreciate a
timely review to keep the submission on track. Thanks.
Regards,
Bhagyada.
prev parent reply other threads:[~2026-09-25 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 14:06 [PATCH v1 0/3] raw/ntb: add AMD NTB support Raghavendra Ningoji
2026-08-23 14:06 ` [PATCH v1 1/3] raw/ntb: generalize framework for multiple vendors Raghavendra Ningoji
2026-09-18 15:06 ` Bruce Richardson
2026-09-21 6:13 ` Raghavendra Ningoji
2026-08-23 14:06 ` [PATCH v1 2/3] raw/ntb: add AMD NTB support Raghavendra Ningoji
2026-09-25 10:22 ` Bruce Richardson
2026-09-28 10:46 ` Raghavendra Ningoji
2026-08-23 14:06 ` [PATCH v1 3/3] doc: " Raghavendra Ningoji
2026-09-25 10:50 ` Bruce Richardson
2026-09-28 10:47 ` Raghavendra Ningoji
2026-09-11 18:30 ` [PATCH v1 0/3] raw/ntb: " Raghavendra Ningoji
2026-09-16 11:29 ` David Marchand
2026-09-25 9:17 ` Bhagyada Modali [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=20260925091721.2234369-1-bhagyada.modali@amd.com \
--to=bhagyada.modali@amd.com \
--cc=Selwin.Sebastian@amd.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jingjing.wu@intel.com \
--cc=raghavendra.ningoji@amd.com \
--cc=rjarry@redhat.com \
--cc=sachin.saxena@oss.nxp.com \
--cc=thomas@monjalon.net \
/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