From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755741AbbCFPJx (ORCPT <rfc822;w@1wt.eu>);
	Fri, 6 Mar 2015 10:09:53 -0500
Received: from mail-ig0-f181.google.com ([209.85.213.181]:38752 "EHLO
	mail-ig0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755687AbbCFPJs (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 6 Mar 2015 10:09:48 -0500
Message-ID: <54F9C339.2050409@mojatatu.com>
Date: Fri, 06 Mar 2015 10:09:45 -0500
From: Jamal Hadi Salim <jhs@mojatatu.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Emil Medve <Emilian.Medve@Freescale.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)
References: <1425534351-1065-1-git-send-email-Emilian.Medve@Freescale.com> <54F84CF1.80702@mojatatu.com> <54F85ECB.3070200@Freescale.com> <54F869CE.1080701@mojatatu.com> <54F87096.2070709@Freescale.com>
In-Reply-To: <54F87096.2070709@Freescale.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Emil,

On 03/05/15 10:04, Emil Medve wrote:
> Hello Jamal,
>
>
> On 03/05/2015 08:35 AM, Jamal Hadi Salim wrote:
>> Hi Emil,
>>
>
> 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
>

Ok, thanks - that was my only concern.
Note there is a lot of offload efforts going on in Linux right now.
Take a look at the proceedings from netdev01. You should take advantage
of that to shape the direction of your patches.
I have suffered at the hands of the sdk for this processor in the past;
it is just a bad idea to keep these SDKs around when Linux can express
the features sufficiently.
Note: The main thing i'd be interested in is when you get to offloading
the classifier/scheduler etc. I know you are focussing on just the 
ethernet level at the moment,

cheers,
jamal