DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: David Marchand <david.marchand@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] i40e: Steps and required configurations of how to achieve the best performance!
Date: Tue, 10 Feb 2015 00:27:12 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A80615E@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CALwxeUuGL1AixyZos9j6vZZ9TP+9AMoP0Cy+mP8=tzSyQuec_Q@mail.gmail.com>

Hi David

It seems we just have minor progress, we have a script which is using setpci to do that.
  [dpdk-dev] scripts: enable extended tag of PCIe (http://www.dpdk.org/dev/patchwork/patch/2762/)

Yes, Stephen's patch could be the direction we need to follow up. Thanks for your indicating that!


From: David Marchand [mailto:david.marchand@6wind.com] 
Sent: Monday, February 9, 2015 8:12 PM
To: Zhang, Helin
Cc: Thomas Monjalon; dev@dpdk.org
Subject: Re: [dpdk-dev] i40e: Steps and required configurations of how to achieve the best performance!

Hello Helin, 

On Thu, Oct 16, 2014 at 2:43 AM, Zhang, Helin <helin.zhang@intel.com> wrote:
Hi Thomas
Yes, your proposal it the perfect one, also the most complicated one. I was thinking of that one as well, but we did not have enough time for that in our 1.8 timeframe.
In the long run, I agree with you to implement EAL function to access PCI config space directly. I will try to put it in our plan as soon as possible, if no objections.
For now, I think the quickest and easiest way might be to write out a script of using ‘setpci’, the Linux command. It is harmless for our code base, and we can remove it when we have better choice. What do you think?
Thank you very much for the great comments on this topic! I really like it!

Did you make any progress on this ?
Actually, looking at Stephen patches (http://dpdk.org/dev/patchwork/patch/3024/), I think we could go with this approach once both uio and vfio are fine.

David Marchand

      reply	other threads:[~2015-02-10  0:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17  4:18 Zhang, Helin
2014-09-17  8:33 ` David Marchand
2014-09-17  8:50   ` Zhang, Helin
2014-09-17 14:03     ` David Marchand
2014-09-18  2:39       ` Zhang, Helin
2014-09-18  8:57         ` David Marchand
2014-09-19  3:43           ` Zhang, Helin
2014-10-15  9:41             ` Thomas Monjalon
2014-10-16  0:43               ` Zhang, Helin
2015-02-09 12:12                 ` David Marchand
2015-02-10  0:27                   ` Zhang, Helin [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:

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

  git send-email \
    --in-reply-to=F35DEAC7BCE34641BA9FAC6BCA4A12E70A80615E@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=david.marchand@6wind.com \
    --cc=dev@dpdk.org \


* 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).