On Fri, May 13, 2016 at 03:45:56PM -0700, Stephen Hurd wrote: > Declare ring structures and a ring free() function. >
Are these rings used for packet RX and TX or something else? > Signed-off-by: Stephen Hurd <stephen.hurd at broadcom.com> > Reviewed-by: Ajit Kumar Khaparde <ajit.khaparde at broadcom.com> > --- > drivers/net/bnxt/Makefile | 1 + > drivers/net/bnxt/bnxt_ring.c | 51 ++++++++++++++++++++++++ > drivers/net/bnxt/bnxt_ring.h | 92 > ++++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 144 insertions(+) > create mode 100644 drivers/net/bnxt/bnxt_ring.c > create mode 100644 drivers/net/bnxt/bnxt_ring.h > > diff --git a/drivers/net/bnxt/Makefile b/drivers/net/bnxt/Makefile > index c57afaa..757ea62 100644 > --- a/drivers/net/bnxt/Makefile > +++ b/drivers/net/bnxt/Makefile > @@ -50,6 +50,7 @@ EXPORT_MAP := rte_pmd_bnxt_version.map > # > SRCS-$(CONFIG_RTE_LIBRTE_BNXT_PMD) += bnxt_ethdev.c > SRCS-$(CONFIG_RTE_LIBRTE_BNXT_PMD) += bnxt_hwrm.c > +SRCS-$(CONFIG_RTE_LIBRTE_BNXT_PMD) += bnxt_ring.c > SRCS-$(CONFIG_RTE_LIBRTE_BNXT_PMD) += bnxt_vnic.c > > # > diff --git a/drivers/net/bnxt/bnxt_ring.c b/drivers/net/bnxt/bnxt_ring.c > new file mode 100644 > index 0000000..0434b07 > --- /dev/null > +++ b/drivers/net/bnxt/bnxt_ring.c > @@ -0,0 +1,51 @@ > +/*- > + * BSD LICENSE > + * > + * Copyright(c) Broadcom Limited. > + * All rights reserved. > + * > + * Redistribution and use in source and binary forms, with or without > + * modification, are permitted provided that the following conditions > + * are met: > + * > + * * Redistributions of source code must retain the above copyright > + * notice, this list of conditions and the following disclaimer. > + * * Redistributions in binary form must reproduce the above copyright > + * notice, this list of conditions and the following disclaimer in > + * the documentation and/or other materials provided with the > + * distribution. > + * * Neither the name of Broadcom Corporation nor the names of its > + * contributors may be used to endorse or promote products derived > + * from this software without specific prior written permission. > + * > + * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS > + * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT > + * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR > + * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT > + * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, > + * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT > + * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, > + * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY > + * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT > + * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE > + * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. > + */ > + > +#include "bnxt.h" > +#include "bnxt_ring.h" > + > +/* > + * Generic ring handling > + */ > + > +void bnxt_free_ring(struct bnxt_ring_struct *ring) > +{ > + /* The actual ring is reserved via rte_memzone_reserve API. > + The current document/code indicates that: > + "Note: A reserved zone cannot be freed." I don't believe this is true any more. With recent changes to base memzones on malloc library, the memzones should be free-able. /Bruce