DPDK patches and discussions
 help / color / mirror / Atom feed
From: "O'driscoll, Tim" <tim.o'driscoll@intel.com>
To: Tetsuya Mukawa <mukawa@igel.co.jp>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] DPDK Features for Q1 2015
Date: Thu, 23 Oct 2014 10:04:50 +0000
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C3FF82@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <544870C9.3050606@igel.co.jp>

> From: Tetsuya Mukawa [mailto:mukawa@igel.co.jp]
> (2014/10/22 22:48), O'driscoll, Tim wrote:
> > PCI Hot Plug: When you migrate a VM, you need hot plug support as the
> new VF on the new hardware you are running on post-migration needs to be
> initialized. With an emulated NIC migration is seamless as all configuration for
> the NIC is within the RAM of the VM and the hypervisor. With a VF you have
> actual hardware in the picture which needs to be set up properly.
> I have patch series for that feature.
> The patches add feature that DPDK apps can attach and detach physical NIC
> ports and virtual device ports at runtime.
> Also I have patches for testpmd to attach and detach ports dynamically.
> For example, after patching, we can type following commands.
> testpmd> port attach p 0000:02:00.0
> testpmd> port attach v eth_pcap0,iface=eth0 port detach p <detaching
> testpmd> port_id> port detach v <detaching port_id>
> (These are just RFC.)
> Now I am collecting up patches to submit to dpdk.org. So I can send RFC
> patches soon. Hopefully next week.

That's great. I also heard privately from another person who is also working on patches for this. If you can submit an RFC, then we should be able to have a discussion on it and avoid duplication of effort.


  reply	other threads:[~2014-10-23  9:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 13:48 O'driscoll, Tim
2014-10-22 14:20 ` [dpdk-dev] " Thomas Monjalon
2014-10-22 14:44   ` Zhou, Danny
2014-10-22 15:05     ` Liang, Cunming
2014-10-22 16:10 ` [dpdk-dev] [dpdk-announce] " Luke Gorrie
2014-10-23 12:29   ` O'driscoll, Tim
2014-10-22 19:22 ` Matthew Hall
2014-10-24  8:10   ` O'driscoll, Tim
2014-10-24 10:10     ` Thomas Monjalon
2014-10-24 19:02       ` Matthew Hall
2014-10-24 19:01     ` Matthew Hall
2014-10-23  3:06 ` Tetsuya Mukawa
2014-10-23 10:04   ` O'driscoll, Tim [this message]
2014-10-23  3:17 ` Tetsuya Mukawa
2014-10-23 11:27   ` O'driscoll, Tim
2014-10-31 22:05   ` Xie, Huawei
2014-11-02 12:50     ` Tetsuya Mukawa
2014-10-23 14:18 ` [dpdk-dev] Fwd: " Jay Rolette
2014-10-23 14:52   ` Alex Markuze

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=26FA93C7ED1EAA44AB77D62FBE1D27BA54C3FF82@IRSMSX102.ger.corp.intel.com \
    --to=tim.o'driscoll@intel.com \
    --cc=dev@dpdk.org \
    --cc=mukawa@igel.co.jp \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git