All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Aaron Conole <aconole@redhat.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 2.3] tools/dpdk_nic_bind.py: Verbosely warn the user on bind
Date: Tue, 01 Mar 2016 00:38:34 -0800 (PST)	[thread overview]
Message-ID: <1640541.74OgNbrBZB@xps13> (raw)
In-Reply-To: <CALwxeUsdiiMUDLMGkECvQmsVkaHr3NWcdzKoHRRcwv6MsLLFRQ@mail.gmail.com>

2016-01-26 21:21, David Marchand:
> 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.

These "auto-hotplug" patches won't be ready for 16.04.
But it's possible to use a new bound device with rte_eth_dev_attach().
So this patch is rejected.

      reply	other threads:[~2016-03-01  8:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 16:20 [PATCH 2.3] tools/dpdk_nic_bind.py: Verbosely warn the user on bind Aaron Conole
2016-01-26 19:25 ` Aaron Conole
2016-01-26 20:14 ` Thomas Monjalon
2016-01-26 20:21   ` David Marchand
2016-03-01  8:38     ` Thomas Monjalon [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=1640541.74OgNbrBZB@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=aconole@redhat.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 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.