public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v3 2/2] doc: add device hotplug documentation
Date: Thu, 26 Feb 2026 14:28:00 +0100	[thread overview]
Message-ID: <2723c0d2-c58b-483b-a5b4-7e2dcd15d3e0@intel.com> (raw)
In-Reply-To: <20260225082525.5fc3e0a2@phoenix.local>

On 2/25/2026 5:25 PM, Stephen Hemminger wrote:
> On Wed, 25 Feb 2026 11:52:25 +0000
> Anatoly Burakov <anatoly.burakov@intel.com> wrote:
> 
>> Currently, device hotplug is not documented except in API headers. Add
>> documentation for device hotplug, both for user facing side of it, and a
>> high level overview of its internal workings.
>>
>> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
>> ---
>>
>> Notes:
>>      v2:
>>      - Removed "summary" section
>>
>>   doc/guides/prog_guide/dev_args.rst       |   3 +
>>   doc/guides/prog_guide/device_hotplug.rst | 286 +++++++++++++++++++++++
>>   doc/guides/prog_guide/index.rst          |   1 +
>>   3 files changed, 290 insertions(+)
>>   create mode 100644 doc/guides/prog_guide/device_hotplug.rst
> 
> 
> This is great to see. It would be the flow from kernel to udev/systemd was explained.

Strictly speaking this isn't DPDK scope, but I've added it to v4 anyway.

> If I remember right, mlx does this through another IB mechanism.
> Also mention this is Linux only.
> 

In the spirit of using AI for everything, since I have no idea how mlx 
works, I've offloaded writing this section to AI :P

-- 
Thanks,
Anatoly

  reply	other threads:[~2026-02-26 13:28 UTC|newest]

Thread overview: 18+ 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
2026-01-05  9:11       ` Burakov, Anatoly
2025-12-19 13:57   ` [PATCH v2 1/2] doc: add devargs documentation Bruce Richardson
2026-02-25 11:52 ` [PATCH v3 " Anatoly Burakov
2026-02-25 11:52   ` [PATCH v3 2/2] doc: add device hotplug documentation Anatoly Burakov
2026-02-25 16:25     ` Stephen Hemminger
2026-02-26 13:28       ` Burakov, Anatoly [this message]
2026-02-26 13:30 ` [PATCH v4 1/2] doc: add devargs documentation Anatoly Burakov
2026-02-26 13:30   ` [PATCH v4 2/2] doc: add device hotplug documentation Anatoly Burakov
2026-03-27 12:32     ` Mcnamara, John
2026-03-27 12:33   ` [PATCH v4 1/2] doc: add devargs documentation Mcnamara, John
2026-03-31 16:13     ` 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=2723c0d2-c58b-483b-a5b4-7e2dcd15d3e0@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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