netdev - Re: [PATCH 0/7] Freescale DPAA FMan FLIB(s)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <54F85ECB.3070200@Freescale.com>
Date:	Thu, 5 Mar 2015 07:48:59 -0600
From:	Emil Medve <Emilian.Medve@...escale.com>
To:	Jamal Hadi Salim <jhs@...atatu.com>,
	<linuxppc-dev@...ts.ozlabs.org>, <netdev@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
CC:	Igal Liberman <Igal.Liberman@...escale.com>
Subject: Re: [PATCH 0/7] Freescale DPAA FMan FLIB(s)

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@...escale.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html