Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754753AbbDTI61 (ORCPT ); Mon, 20 Apr 2015 04:58:27 -0400 Received: from mail-bn1bn0106.outbound.protection.outlook.com ([157.56.110.106]:37763 "EHLO na01-bn1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754142AbbDTI6X convert rfc822-to-8bit (ORCPT ); Mon, 20 Apr 2015 04:58:23 -0400 From: "Igal.Liberman@freescale.com" To: Kumar Gala CC: "linuxppc-dev@lists.ozlabs.org" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Scott Wood , Madalin-Cristian Bucur Subject: RE: [RFC,1/8] soc/fman: Add FMan MURAM support Thread-Topic: [RFC,1/8] soc/fman: Add FMan MURAM support Thread-Index: AQHQW9t8INPwoxczz02iOSdTb1ZtV50ZApyAgDzQ8MA= Date: Mon, 20 Apr 2015 08:58:20 +0000 Message-ID: References: <1426050469-12507-1-git-send-email-igal.liberman@freescale.com> <32CF85E2-A8AA-454D-A46F-0E778DAF97ED@kernel.crashing.org> In-Reply-To: <32CF85E2-A8AA-454D-A46F-0E778DAF97ED@kernel.crashing.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.88.162.1] authentication-results: kernel.crashing.org; dkim=none (message not signed) header.d=none; x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR03MB560; x-forefront-antispam-report: BMV:1;SFV:NSPM;SFS:(10019020)(6009001)(13464003)(24454002)(51704005)(377454003)(74316001)(92566002)(54356999)(76176999)(76576001)(33656002)(19580405001)(86362001)(66066001)(77156002)(19580395003)(46102003)(40100003)(110136001)(2950100001)(2900100001)(99286002)(122556002)(62966003)(87936001)(50986999)(106116001)(77096005)(2656002)(102836002)(4001430100001);DIR:OUT;SFP:1102;SCL:1;SRVR:DM2PR03MB560;H:DM2PR03MB383.namprd03.prod.outlook.com;FPR:;SPF:None;MLV:sfv;LANG:en; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(601004)(5002010)(5005006);SRVR:DM2PR03MB560;BCL:0;PCL:0;RULEID:;SRVR:DM2PR03MB560; x-forefront-prvs: 05529C6FDB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-OriginatorOrg: freescale.com X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2015 08:58:20.5710 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 710a03f5-10f6-4d38-9ff4-a80b81da590d X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR03MB560 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1759 Lines: 49 Regards, Igal Liberman. > -----Original Message----- > From: Kumar Gala [mailto:galak@kernel.crashing.org] > Sent: Thursday, March 12, 2015 5:57 PM > To: Liberman Igal-B31950 > Cc: linuxppc-dev@lists.ozlabs.org; netdev@vger.kernel.org; linux- > kernel@vger.kernel.org; Wood Scott-B07421 > Subject: Re: [RFC,1/8] soc/fman: Add FMan MURAM support > > > On Mar 11, 2015, at 12:07 AM, Igal.Liberman > wrote: > > > From: Igal Liberman > > > > Add Frame Manager Multi-User RAM support. > > > > Signed-off-by: Igal Liberman > > --- > > drivers/soc/fsl/fman/Kconfig | 1 + > > drivers/soc/fsl/fman/Makefile | 5 +- > > drivers/soc/fsl/fman/fm_muram.c | 174 > +++++++++++++++++++++++++++++++ > > drivers/soc/fsl/fman/inc/fm_muram_ext.h | 98 +++++++++++++++++ > > 4 files changed, 276 insertions(+), 2 deletions(-) create mode 100644 > > drivers/soc/fsl/fman/fm_muram.c create mode 100644 > > drivers/soc/fsl/fman/inc/fm_muram_ext.h > > > > use lib/genalloc instead of rheap > Hi Kumar, I looked into lib/genalloc allocator. As far as I see, the genalloc allocator doesn't allow to control the memory alignment when you allocate a chunk of memory. Two important notes regarding MURAM memory: - The allocated memory chunks should have specific alignment (might be different in each chunk). - The allocations must be efficient, we don't want to "waste" MURAM due to alignment issues. > - k -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/