[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20151129.210210.1777978635596463961.davem@davemloft.net>
Date: Sun, 29 Nov 2015 21:02:10 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: mw@...ihalf.com
Cc: f.fainelli@...il.com, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, netdev@...r.kernel.org,
thomas.petazzoni@...e-electrons.com, andrew@...n.ch,
linux@....linux.org.uk, jason@...edaemon.net, myair@...vell.com,
jaz@...ihalf.com, simon.guinot@...uanux.org, xswang@...vell.com,
nadavh@...vell.com, alior@...vell.com, tn@...ihalf.com,
gregory.clement@...e-electrons.com, nitroshift@...oo.com,
sebastian.hesselbarth@...il.com
Subject: Re: [PATCH 00/13] mvneta Buffer Management and enhancements
From: Marcin Wojtas <mw@...ihalf.com>
Date: Sun, 29 Nov 2015 14:21:35 +0100
>> Looking at your patches, it was not entirely clear to me how the buffer
>> manager on these Marvell SoCs work, but other networking products have
>> something similar, like Broadcom's Cable Modem SoCs (BCM33xx) FPM, and
>> maybe Freescale's FMAN/DPAA seems to do something similar.
>>
>> Does the buffer manager allocation work by giving you a reference/token
>> to a buffer as opposed to its address? If that is the case, it would be
>> good to design support for such hardware in a way that it can be used by
>> more drivers.
>
> It does not operate on a reference/token but buffer pointers (physical
> adresses). It's a ring and you cannot control which buffer will be
> taken at given moment.
He understands this, he's asking you to make an "abstraction".
FWIW, I know of at least one more chip that operates this way too and
the code I wrote for it, particularly the buffer management, took a
while to solidify. Common helpers for this kind of situation would
have helped me back when I wrote it.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists