From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Burakov,
Anatoly"
<anatoly.burakov-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: IGB_UIO port unbinding
Date: Thu, 10 Apr 2014 13:39:54 +0200 [thread overview]
Message-ID: <2817508.QMqjK3mPRB@xps13> (raw)
In-Reply-To: <C6ECDF3AB251BE4894318F4E451236975927405D-kPTMFJFq+rGvNW/NfzhIbrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Hi,
2014-04-10 09:39, Burakov, Anatoly:
> As you may or may not know, the CONFIG_RTE_EAL_UNBIND_PORTS was deprecated
> in the official Intel(r) DPDK 1.6.0 release package. However, the code
> itself (e.g. in lib/librte_eal/linuxapp/eal_pci.c and other places) to
> support that config option was not removed. My question would be, would
> anyone be opposed to a patch to remove that code entirely? E.g. does anyone
> use that functionality?
On my side, it's OK to remove it.
I think you can prepare the patch and we'll wait 1 week before applying it.
If nobody complains, this feature will be definitely removed.
--
Thomas
next prev parent reply other threads:[~2014-04-10 11:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 9:39 IGB_UIO port unbinding Burakov, Anatoly
[not found] ` <C6ECDF3AB251BE4894318F4E451236975927405D-kPTMFJFq+rGvNW/NfzhIbrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-04-10 11:39 ` Thomas Monjalon [this message]
2014-04-10 16:04 ` Prashant Upadhyaya
[not found] ` <C7CE7EEF248E2B48BBA63D0ABEEE700C61FB7E01C1-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2014-04-11 8:43 ` Thomas Monjalon
2014-04-11 8:59 ` Burakov, Anatoly
[not found] ` <C6ECDF3AB251BE4894318F4E451236975927459B-kPTMFJFq+rGvNW/NfzhIbrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-04-11 9:06 ` Prashant Upadhyaya
[not found] ` <C7CE7EEF248E2B48BBA63D0ABEEE700C61FB7E02A6-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2014-04-11 9:19 ` Burakov, Anatoly
2014-04-11 16:24 ` Stephen Hemminger
[not found] ` <20140411092435.29e06974-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2014-04-14 8:57 ` Burakov, Anatoly
[not found] ` <C6ECDF3AB251BE4894318F4E451236975927DC44-kPTMFJFq+rF9qrmMLTLiibfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-04-14 15:33 ` Stephen Hemminger
[not found] ` <20140414083303.09cb43ed-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2014-04-14 15:40 ` Burakov, Anatoly
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=2817508.QMqjK3mPRB@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=anatoly.burakov-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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).