From: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
To: jigsaw <jigsaw@gmail.com>, Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] 82599 SR-IOV with passthrough
Date: Thu, 17 Oct 2013 17:25:34 +0530 [thread overview]
Message-ID: <C7CE7EEF248E2B48BBA63D0ABEEE700C43EA664331@GUREXMB01.ASIAN.AD.ARICENT.COM> (raw)
In-Reply-To: <CAHVfvh7t7PZtxo5fpdzPGtoBjT+XwTWYUPGOwu0P-WMQima7jA@mail.gmail.com>
Hi Qinglai,
Why are you using the kernel driver at all.
Use the DPDK driver to control the PF on the host. The guest would communicate with the PF on host using mailbox as usual.
Then the changes will be limited to DPDK, isn't it ?
Regards
-Prashant
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of jigsaw
Sent: Wednesday, October 16, 2013 6:51 PM
To: Thomas Monjalon
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] 82599 SR-IOV with passthrough
Hi Thomas,
Thanks for reply.
The kernel has older version of PF than the one released on sf.net. So I'm checking the sf.net release.
If the change is limited in DPDK then it is controllable. But now it affects Intel's PF driver, I don't even know how to push the feature to Intel. The driver on sf.net is a read-only repository, isn't it? It would be painful to maintain another branch of 10G PF driver.
Could Intel give some advice or hints here?
thx &
rgds,
-Qinglai
On Wed, Oct 16, 2013 at 3:58 PM, Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> 16/10/2013 14:18, jigsaw :
>> Therefore, to add support for multiple queues per VF, we have to at
>> least fix the PF driver, then add support in DPDK's VF driver.
>
> You're right, Linux PF driver have to be updated to properly manage
> multiple queues per VF. Then the guest can be tested with DPDK or with
> Linux driver (ixgbe_vf).
>
> Note that there are 2 versions of Linux driver for ixgbe: kernel.org
> and sourceforge.net (supporting many kernel versions).
>
> --
> Thomas
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
next prev parent reply other threads:[~2013-10-17 11:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 12:18 jigsaw
2013-10-16 12:58 ` Thomas Monjalon
2013-10-16 13:20 ` jigsaw
2013-10-17 11:55 ` Prashant Upadhyaya [this message]
2013-10-17 12:43 ` jigsaw
2013-10-17 12:54 ` jigsaw
2013-10-17 13:02 ` Prashant Upadhyaya
2013-10-17 13:11 ` jigsaw
2013-10-17 13:47 ` Thomas Monjalon
2013-10-17 13:52 ` jigsaw
2013-10-17 11:52 ` Prashant Upadhyaya
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=C7CE7EEF248E2B48BBA63D0ABEEE700C43EA664331@GUREXMB01.ASIAN.AD.ARICENT.COM \
--to=prashant.upadhyaya@aricent.com \
--cc=dev@dpdk.org \
--cc=jigsaw@gmail.com \
--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).