linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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 09:04:54 -0600	[thread overview]
Message-ID: <54F87096.2070709@Freescale.com> (raw)
In-Reply-To: <54F869CE.1080701@mojatatu.com>

Hello Jamal,


On 03/05/2015 08:35 AM, Jamal Hadi Salim wrote:
> Hi Emil,
> 
> On 03/05/15 08:48, Emil Medve wrote:
> 
>> 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
> 
> Meaning? Let me ask the question differently:
> Do i need your sdk to use the features exposed

No. All the kernel drivers/code we want to upstream is meant to stand on
its own and be used the "normal" Linux/Unix way

> or can i use something
> like tc to set up the deficit rr or wred or the exposed classifiers
> and associated actions?

The SDK doesn't currently support the enablement of any HW QoS features
via standard Linux user-space tools. The SDK contains some FSL tools for
that. As a time moving target we intend to support lots of the DPAA
features via standard kernel/user-space means: ethtool, iptables,
iproute2, etc.

> Would your sdk (via user space direct programming) benefit because you
> have pushed these pieces into the kernel?

Not specifically because of the kernel drivers. In support for the
user-space DPAA the kernel will have some UIO/VFIO drivers to allow the
user-space to "mmap" these devices (portals, ports, MAC(s), etc.). The
intent is to use the same driver sources for the kernel- and user-space
drivers

>>> How are you planning to
>>> add support for your classifiers, queue schedulers etc?
>>
>> Yes
> 
> Yes as in these will be available via linux kernel or via your sdk?

As in these will be available via familiar kernel-/user-space tools

>>> 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)
> 
> the sdk is open source?

I'm uncertain about *all* the licenses included, but you can look into
it and download the SDK via git.freescale.com and/or
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=SDKLINUX


Cheers,

  reply	other threads:[~2015-03-05 15:04 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
2015-03-05 14:35     ` Jamal Hadi Salim
2015-03-05 15:04       ` Emil Medve [this message]
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=54F87096.2070709@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).