From: Tetsuya Mukawa <mukawa@igel.co.jp>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] ethdev cleanup following hotplug changes
Date: Tue, 21 Jul 2015 08:49:20 +0900 [thread overview]
Message-ID: <CAKU8wkdHHCA8EUp_+mCPNkwfj5w8agmx1hsEuGNd0EPagm1bng@mail.gmail.com> (raw)
In-Reply-To: <6716150.9oBPbZhtzg@xps13>
2015-07-17 18:31 GMT+09:00 Thomas Monjalon <thomas.monjalon@6wind.com>:
> Hi Tetsuya,
Hi Thomas,
Sorry for late reply. I am out of office now, and will back to tomorrow.
>
> Any news about this comment in ethdev?
>
> * TODO:
> * rte_eal_vdev_init() should return port_id,
> * And rte_eth_dev_save() and rte_eth_dev_get_changed_port()
> * should be removed. */
>
> http://dpdk.org/browse/dpdk/tree/lib/librte_ether/rte_ethdev.c#n618
So far, I don't have patch for that, also unfortunately, it may be
difficult to have time in next few weeks.
So I will submit the patch for DPDK-2.2. Will that fit your schedule?
(Also, I will submit hotplug patch to support vfio devices for
DPDK-2.2, if I can have time and anyone doesn't submit.)
Regards,
Tetsuya
next prev parent reply other threads:[~2015-07-20 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 9:31 Thomas Monjalon
2015-07-20 23:49 ` Tetsuya Mukawa [this message]
2015-07-21 8:10 ` 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=CAKU8wkdHHCA8EUp_+mCPNkwfj5w8agmx1hsEuGNd0EPagm1bng@mail.gmail.com \
--to=mukawa@igel.co.jp \
--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).