From: Stephen Hemminger <stephen@networkplumber.org>
To: Cliff Burdick <cburdick@nvidia.com>
Cc: <dev@dpdk.org>, <anatoly.burakov@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH 1/2] eal: support dmabuf
Date: Wed, 28 Jan 2026 17:51:07 -0800 [thread overview]
Message-ID: <20260128175107.26fe3189@phoenix.local> (raw)
In-Reply-To: <20260127174429.1504288-2-cburdick@nvidia.com>
On Tue, 27 Jan 2026 17:44:08 +0000
Cliff Burdick <cburdick@nvidia.com> wrote:
> +/**
> + * Get dma-buf file descriptor associated with a memseg list.
> + *
> + * @note This function does not perform any locking, and is only safe to call
> + * from within memory-related callback functions.
Maybe warning instead of note.
> + *
> + * @param msl
> + * A pointer to memseg list for which to get dma-buf fd.
> + *
> + * @return
> + * Valid dma-buf file descriptor (>= 0) in case of success.
> + * -1 if not dma-buf backed or in case of error, with ``rte_errno`` set to:
> + * - EINVAL - ``msl`` pointer was NULL or did not point to a valid memseg list
> + */
> +int
> +rte_memseg_list_get_dmabuf_fd_thread_unsafe(const struct rte_memseg_list *msl);
ENAMETOOLONG
At some point, you need to come up with a better naming convention.
next prev parent reply other threads:[~2026-01-29 1:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 17:44 [PATCH 0/2] support dmabuf Cliff Burdick
2026-01-27 17:44 ` [PATCH 1/2] eal: " Cliff Burdick
2026-01-29 1:48 ` Stephen Hemminger
2026-01-29 1:51 ` Stephen Hemminger [this message]
2026-01-27 17:44 ` [PATCH 2/2] common/mlx5: " Cliff Burdick
2026-01-27 19:21 ` [REVIEW] " Stephen Hemminger
2026-01-28 14:30 ` David Marchand
2026-01-28 17:10 ` Stephen Hemminger
2026-01-28 17:43 ` Stephen Hemminger
2026-02-03 17:34 ` Cliff Burdick
2026-01-29 1:51 ` [PATCH 2/2] " Stephen Hemminger
2026-01-28 0:04 ` [PATCH 0/2] " Stephen Hemminger
2026-02-03 17:18 ` Cliff Burdick
2026-02-03 22:26 ` [PATCH v2 " Cliff Burdick
2026-02-03 22:26 ` [PATCH v2 1/2] eal: " Cliff Burdick
2026-02-03 22:26 ` [PATCH v2 2/2] common/mlx5: " Cliff Burdick
2026-02-03 23:02 ` [PATCH v3 0/2] " Cliff Burdick
2026-02-03 23:02 ` [PATCH v3 1/2] eal: " Cliff Burdick
2026-02-03 23:02 ` [PATCH v3 2/2] common/mlx5: " Cliff Burdick
2026-02-04 15:50 ` [PATCH v4 0/2] " Cliff Burdick
2026-02-04 15:50 ` [PATCH v4 1/2] eal: " Cliff Burdick
2026-02-12 13:57 ` Burakov, Anatoly
2026-04-23 17:06 ` Cliff Burdick
2026-02-04 15:50 ` [PATCH v4 2/2] common/mlx5: " Cliff Burdick
2026-02-05 18:48 ` [PATCH v4 0/2] " Stephen Hemminger
2026-02-05 20:25 ` Cliff Burdick
2026-02-05 22:50 ` Stephen Hemminger
2026-03-31 3:15 ` Stephen Hemminger
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=20260128175107.26fe3189@phoenix.local \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=cburdick@nvidia.com \
--cc=dev@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.