From: Thomas Monjalon <thomas@monjalon.net>
To: 许玲燕 <lingyan.xu@metax-tech.com>
Cc: dev <dev@dpdk.org>, eagostini <eagostini@nvidia.com>
Subject: Re: [PATCH] gpu/metax: add new driver for Metax GPU
Date: Tue, 02 Jun 2026 12:01:49 +0200 [thread overview]
Message-ID: <CsAn75rzSb2jiQLRSeXkmQ@monjalon.net> (raw)
In-Reply-To: <6c18e957-c1c2-4b43-9b2c-b36424c1e9af.lingyan.xu@metax-tech.com>
Hello,
01/06/2026 07:47, 许玲燕:
> I am writing to propose a new driver for the Metax GPU,
How do you access the GPU?
Are you using a specific library or kernel module?
> which I believe will significantly enhance our support
> and performance for this hardware.
> The patch attached includes the initial implementation of the driver,
> with key features such as:
>
> * Basic initialization and configuration
> * Memory management and allocation
> * Core functionality for rendering and compute tasks
I am familiar with connecting compute tasks of a GPU
with DPDK networking, but I'm surprised by the rendering functionality.
Do you mean graphical rendering of data coming from the network?
> Please review the code and let me know if you have any feedback or suggestions.
> I am more than happy to make any necessary adjustments and improvements.
Thank you for working on this.
I recommend following this guide to introduce a new driver:
https://doc.dpdk.org/guides/contributing/new_driver.html
next prev parent reply other threads:[~2026-06-02 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 5:47 [PATCH] gpu/metax: add new driver for Metax GPU 许玲燕
2026-06-02 10:01 ` Thomas Monjalon [this message]
2026-06-09 10:22 ` 回复：[PATCH] " 许玲燕
2026-06-09 10:43 ` Thomas Monjalon
2026-06-11 7:10 ` 回复：回复：[PATCH] " 许玲燕
2026-06-11 9:17 ` [PATCH] " Thomas Monjalon
2026-06-12 7:19 ` 回复：[PATCH] " 许玲燕
2026-06-12 14:49 ` Thomas Monjalon
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=CsAn75rzSb2jiQLRSeXkmQ@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=eagostini@nvidia.com \
--cc=lingyan.xu@metax-tech.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