DPDK usage discussions
 help / color / mirror / Atom feed
From: Ran Shalit <ranshalit@gmail.com>
To: Vincent JARDIN <vincent.jardin@6wind.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Support for cavium Octeon ?
Date: Tue, 9 Feb 2016 20:13:53 +0200	[thread overview]
Message-ID: <CAJ2oMhLURHjXhycw2etdMobcaZE4c_VPqWDJZTwHde1G_OvmPA@mail.gmail.com> (raw)
In-Reply-To: <CAG8AbRWahidNAGs3__B0Z79wM6Pg_BdsrhJLiKvgixWWJZYTVw@mail.gmail.com>

On Tue, Feb 9, 2016 at 5:51 PM, Vincent JARDIN <vincent.jardin@6wind.com> wrote:
>
> Le 9 févr. 2016 09:48, "Ran Shalit" <ranshalit@gmail.com> a écrit :
>>
>>  Does dpdk support Cavium Octeon with PCI express ?
>> I see there is Nitrox library, where can I read more about it ?
>>
>>
>> On Mon, Feb 8, 2016 at 5:05 PM, Ran Shalit <ranshalit@gmail.com> wrote:
>> > Hello,
>> >
>> > Does dpdk support Cavium Octeon 73xx ?
>> > We need to develop application over PCIe between intel cpu and Cavium
>> > Octeon.
>> > I wander if it should work with Cavium Octeon or only with Intel's cpu ?
>> >
>
> Can you explain?
>
> Nitrox is not CN73xx, so why both questions?
>
> 6WIND made such support with Nitrox and DPDK. Because of some Nitrox SDK's
> constrains, it uses DPDK API under source licensing directly from 6WIND.
> Feel free to contact us.
>
> Best regards,
>   Vincent

Hi,

Right. Seems that I mixed things.
So, as to the first question, do you suppose that dpdk can be used
with  Cavium Octeon 73xx ?
Will it know how to access the PCI express in Cavium ?

Thanks,
Ran

  reply	other threads:[~2016-02-09 18:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 15:05 Ran Shalit
2016-02-09  8:47 ` Ran Shalit
2016-02-09 15:15   ` Muhammad Zain-ul-Abideen
2016-02-09 15:51   ` Vincent JARDIN
2016-02-09 18:13     ` Ran Shalit [this message]
2016-02-10 11:02       ` Muhammad Zain-ul-Abideen

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=CAJ2oMhLURHjXhycw2etdMobcaZE4c_VPqWDJZTwHde1G_OvmPA@mail.gmail.com \
    --to=ranshalit@gmail.com \
    --cc=users@dpdk.org \
    --cc=vincent.jardin@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).