From: Stephen Hemminger <stephen@networkplumber.org>
To: jia.guo@intel.com
Cc: anatoly.burakov@intel.com, arybchenko@solarflare.com,
bernard.iremonger@intel.com, bruce.richardson@intel.com,
dev@dpdk.org, ferruh.yigit@intel.com, gaetan.rivet@6wind.com,
konstantin.ananyev@intel.com, matan@mellanox.com,
qi.z.zhang@intel.com, shahafs@mellanox.com,
shaopeng.he@intel.com, stephen@networkplumber.org,
thomas@monjalon.net, wenzhuo.lu@intel.com
Subject: Re: [PATCH 0/3] use a common eal device event for hot-unplug
Date: Fri, 9 Jun 2023 10:18:53 -0700 [thread overview]
Message-ID: <20230609171853.83113-1-stephen@networkplumber.org> (raw)
In-Reply-To: <1544773540-89825-1-git-send-email-jia.guo@intel.com>
Unifying hotplug and device event support would be good idea
but this patch has gone stale. And supporting it would require
API changes (need to wait for next LTS) and a lot of testing.
Also, hotplug is a complex topic which has a lot of platform
dependencies. If someone wants to do a more general solution
this patchset is worth looking at. But for now it needs to
be marked rejected in patchwork.
prev parent reply other threads:[~2023-06-09 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 7:45 [dpdk-dev] " Jeff Guo
2018-12-14 7:45 ` [dpdk-dev] [PATCH 1/3] eal: add --dev-hotplug option Jeff Guo
2018-12-17 10:15 ` David Marchand
2018-12-29 4:06 ` Jeff Guo
2019-01-02 14:46 ` David Marchand
2018-12-14 7:45 ` [dpdk-dev] [PATCH 2/3] ethdev: remove ethdev rmv interrupt Jeff Guo
2018-12-14 7:45 ` [dpdk-dev] [PATCH 3/3] testpmd: remove device detach into eal Jeff Guo
2019-04-08 14:10 ` [dpdk-dev] [PATCH 0/3] use a common eal device event for hot-unplug Iremonger, Bernard
2019-04-08 14:10 ` Iremonger, Bernard
2023-06-09 17:18 ` Stephen Hemminger [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=20230609171853.83113-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=arybchenko@solarflare.com \
--cc=bernard.iremonger@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gaetan.rivet@6wind.com \
--cc=jia.guo@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=matan@mellanox.com \
--cc=qi.z.zhang@intel.com \
--cc=shahafs@mellanox.com \
--cc=shaopeng.he@intel.com \
--cc=thomas@monjalon.net \
--cc=wenzhuo.lu@intel.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;
as well as URLs for NNTP newsgroup(s).