From: David Marchand <david.marchand@6wind.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2.3] tools/dpdk_nic_bind.py: Verbosely warn the user on bind
Date: Tue, 26 Jan 2016 21:21:29 +0100 [thread overview]
Message-ID: <CALwxeUsdiiMUDLMGkECvQmsVkaHr3NWcdzKoHRRcwv6MsLLFRQ@mail.gmail.com> (raw)
In-Reply-To: <2190233.dCyjSQMtc6@xps13>
On Tue, Jan 26, 2016 at 9:14 PM, Thomas Monjalon
<thomas.monjalon@6wind.com> wrote:
> 2015-12-11 11:20, Aaron Conole:
>> DPDK ports are only detected during the EAL initialization. After that, any
>> new DPDK ports which are bound will not be visible to the application.
>>
>> The dpdk_nic_bind.py can be a bit more helpful to let users know that DPDK
>> enabled applications will not find rebound ports until after they have been
>> restarted.
>
> I think it's better to improve hotplug and allow hot binding.
> A work is in progress towards this direction.
> David, can you confirm?
I intend to provide some rfc patches later this week, for next release.
--
David Marchand
next prev parent reply other threads:[~2016-01-26 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 16:20 Aaron Conole
2016-01-26 20:14 ` Thomas Monjalon
2016-01-26 20:21 ` David Marchand [this message]
2016-03-01 8:38 ` 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=CALwxeUsdiiMUDLMGkECvQmsVkaHr3NWcdzKoHRRcwv6MsLLFRQ@mail.gmail.com \
--to=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).