From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Anatoly Burakov" <anatoly.burakov@intel.com>, <dev@dpdk.org>
Subject: RE: [PATCH v2 2/2] doc: add device hotplug documentation
Date: Fri, 19 Dec 2025 15:01:54 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F655FB@smartserver.smartshare.dk> (raw)
In-Reply-To: <e3bb33543d6a405874c89efeed15f01cefea3f83.1766150746.git.anatoly.burakov@intel.com>
> +Device Hotplug
> +==============
> +
> +Introduction
> +------------
> +
> +Device hotplug refers to the ability to attach and detach devices at
> runtime, after the initial EAL initialization has completed.
> +This feature allows applications to dynamically add or remove physical
> or virtual devices while the DPDK application is running.
> +
> +.. note::
> + Device hotplug does not support multiprocess operation nor kernel
> device event notifications on platforms other than Linux.
Does this mean:
Device hotplug does not support "multiprocess operation" nor "kernel device event notifications on platforms other than Linux".
Or:
Device hotplug does not support "multiprocess operation nor kernel device event notifications" on platforms other than Linux.
Please make this note more clear. My English skills are not good enough to understand.
next prev parent reply other threads:[~2025-12-19 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 12:13 [PATCH v1 1/2] doc: add devargs documentation Anatoly Burakov
2025-11-14 12:13 ` [PATCH v1 2/2] doc: add device hotplug documentation Anatoly Burakov
2025-11-30 15:44 ` [PATCH v1 1/2] doc: add devargs documentation Thomas Monjalon
2025-12-02 17:35 ` Burakov, Anatoly
2025-12-19 13:25 ` [PATCH v2 " Anatoly Burakov
2025-12-19 13:25 ` [PATCH v2 2/2] doc: add device hotplug documentation Anatoly Burakov
2025-12-19 14:01 ` Morten Brørup [this message]
2025-12-19 13:57 ` [PATCH v2 1/2] doc: add devargs documentation Bruce Richardson
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=98CBD80474FA8B44BF855DF32C47DC35F655FB@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
/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).