DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org, qi.z.zhang@intel.com, beilei.xing@intel.com, "Liu,
	Lingyu" <lingyu.liu@intel.com>
Cc: "Cao, Yahui" <yahui.cao@intel.com>
Subject: Re: [PATCH v4] doc: add iavf live migration guide
Date: Thu, 27 Jul 2023 12:42:35 +0200	[thread overview]
Message-ID: <6584058.uKWtJMOXK1@thomas> (raw)
In-Reply-To: <b380a63d-e68c-99ea-7226-d6cd595ee29c@intel.com>

27/07/2023 10:34, Liu, Lingyu:
> 
> On 7/12/2023 3:54 AM, Thomas Monjalon wrote:
> > Hello,
> >
> > I don't pull this patch in -rc3 because I feel some improvements should be done.
> >
> Hi Thomas, thanks for your review. I am sorry for the late response.
> 
> >> On 7/7/2023 2:08 PM, Lingyu Liu wrote:
> >>> +        echo 2 > /sys/bus/pci/devices/0000:ca:00.1/sriov_numvfs
> >>> +        echo "8086 1889" > /sys/bus/pci/drivers/ice-vfio-pci/new_id
> >>> +        echo 0000:ca:11.0 > /sys/bus/pci/devices/0000:ca:11.0/driver/unbind
> >>> +        echo 0000:ca:11.0 > /sys/bus/pci/drivers/ice-vfio-pci/bind
> >>> +        echo 0000:ca:11.1 > /sys/bus/pci/devices/0000:ca:11.1/driver/unbind
> >>> +        echo 0000:ca:11.1 > /sys/bus/pci/drivers/ice-vfio-pci/bind
> > Why not using dpdk-devbind.py?
> 
> dpdk-devbind.py doesn't support ice-vfio-pci driver yet.

So it should be a requirement.
Please work on dpdk-devbind.py




      reply	other threads:[~2023-07-27 10:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03  5:14 [PATCH] doc: add ice VF " Lingyu Liu
2023-07-04  2:27 ` [PATCH V2] doc: add iavf " Lingyu Liu
2023-07-04  5:01   ` Cao, Yahui
2023-07-06  7:24   ` [PATCH v3] " Lingyu Liu
2023-07-07  6:08     ` [PATCH v4] " Lingyu Liu
2023-07-07  6:21       ` Cao, Yahui
2023-07-07  6:41         ` Zhang, Qi Z
2023-07-11 19:54         ` Thomas Monjalon
2023-07-27  8:34           ` Liu, Lingyu
2023-07-27 10:42             ` 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=6584058.uKWtJMOXK1@thomas \
    --to=thomas@monjalon.net \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=lingyu.liu@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=yahui.cao@intel.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).