From: Emil Medve <Emilian.Medve@Freescale.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>,
<linuxppc-dev@lists.ozlabs.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Igal Liberman <Igal.Liberman@Freescale.com>
Subject: Re: [PATCH 0/7] Freescale DPAA FMan FLIB(s)
Date: Thu, 5 Mar 2015 07:48:59 -0600 [thread overview]
Message-ID: <54F85ECB.3070200@Freescale.com> (raw)
In-Reply-To: <54F84CF1.80702@mojatatu.com>
Hello Jamal,
On 03/05/2015 06:32 AM, Jamal Hadi Salim wrote:
> On 03/05/15 00:45, Emil Medve wrote:
>> From: Igal Liberman <Igal.Liberman@freescale.com>
>>
>> The Freescale Data Path Acceleration Architecture (DPAA) is a set of
>> hardware components on specific QorIQ P and T series multicore
>> processors.
>> This architecture provides the infrastructure to support simplified
>> sharing of networking interfaces and accelerators by multiple CPU cores,
>> and the accelerators themselves.
>>
>> One of the DPAA accelerators is the Frame Manager (FMan), which
>> combines the Ethernet network interfaces with packet distribution
>> logic to provide intelligent distribution and queuing decisions for
>> incoming traffic at line rate.
>>
>> This patch presents the FMan Foundation Libraries (FLIB) headers.
>> The FMan FLIB suite adds basic support for the DPAA FMan hardware
>> register access.
>> The FMan FLIB suite is used in Freescale's SDK Releases.
>>
>
> Is this intended to merely enable your sdk?
The intent is to upstream the entire suite of the DPAA drivers. All the
drivers are still WIP, but B/QMan have been already presented to the
upstream community and this is the first attempt to publish (some low
level code of) the FMan driver. As we go through our internal checklist
and in the same time address community feedback we'll soon get the
drivers to be acceptable for the upstream trees
The first version of the actual Ethernet driver will follow imminently
SDK enablement is a side-effect
> How are you planning to
> add support for your classifiers, queue schedulers etc?
Yes
> Is that a patch
> on top of this or it is something that sits on user space?
Both. Full DPAA/Ethernet enablement will be present in the kernel. We
also have support for user-space based approach. I'm unsure where/when
we might publish that. Of course the SDK is always a place you can turn
to for all the code we have (in whatever state it might be)
Cheers.
next prev parent reply other threads:[~2015-03-05 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 5:45 [PATCH 0/7] Freescale DPAA FMan FLIB(s) Emil Medve
2015-03-05 5:45 ` [PATCH 1/7] soc/fman: Add the FMan FLIB headers Emil Medve
2015-03-06 16:32 ` Kumar Gala
2015-03-05 5:45 ` [PATCH 2/7] soc/fman: Add the FMan FLIB Emil Medve
2015-03-07 0:57 ` Scott Wood
2015-03-05 5:45 ` [PATCH 3/7] soc/fman: Add the FMan port FLIB Emil Medve
2015-03-05 5:45 ` [PATCH 4/7] soc/fman: Add the FMan MAC FLIB Emil Medve
2015-03-05 5:45 ` [PATCH 5/7] soc/fman: Add the FMan parser and KeyGen FLIB(s) Emil Medve
2015-03-05 5:45 ` [PATCH 6/7] soc/fman: Add the FMan RTC FLIB Emil Medve
2015-03-05 5:45 ` [PATCH 7/7] soc/fman: Add the FMan SP FLIB Emil Medve
2015-03-05 12:32 ` [PATCH 0/7] Freescale DPAA FMan FLIB(s) Jamal Hadi Salim
2015-03-05 13:48 ` Emil Medve [this message]
2015-03-05 14:35 ` Jamal Hadi Salim
2015-03-05 15:04 ` Emil Medve
2015-03-06 15:09 ` Jamal Hadi Salim
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=54F85ECB.3070200@Freescale.com \
--to=emilian.medve@freescale.com \
--cc=Igal.Liberman@Freescale.com \
--cc=jhs@mojatatu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
/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).