From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH v6 00/38] new bnxt poll mode driver library Date: Tue, 21 Jun 2016 15:46:14 +0100 Message-ID: <20160621144614.GD12008@bricha3-MOBL3> References: <1465944971-113413-1-git-send-email-stephen.hurd@broadcom.com> <1466025818-124223-1-git-send-email-stephen.hurd@broadcom.com> <20160616142444.GA14984@bricha3-MOBL3> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Stephen Hurd , dev@dpdk.org To: Ajit Khaparde Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 60539C314 for ; Tue, 21 Jun 2016 16:46:18 +0200 (CEST) Content-Disposition: inline In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Tue, Jun 21, 2016 at 09:25:18AM -0500, Ajit Khaparde wrote: > Bruce, > We have a set of patches which add support to a couple of new Broadcom = PCI > devices. > Should I use the dpdk-next-net/rel_16_07 to push them out? > Let me know if there is any other way to do this. >=20 > Thanks >=20 They should be based on dpdk-next-net/rel_16_07. However, be aware that it is very late in the DPDK 16.07 release cycle fo= r us to take new content in, so please minimise the patchset to only the chang= es that are absolutely necessary for you. At this stage we can only take contribu= tions on a best-effort basis, so having a smaller patchset will increase your c= hances that the patch may be merged. Regards, /Bruce > On Thu, Jun 16, 2016 at 1:51 PM, Ajit Khaparde > wrote: >=20 > > > > On Thu, Jun 16, 2016 at 9:24 AM, Bruce Richardson < > > bruce.richardson@intel.com> wrote: > > > >> On Wed, Jun 15, 2016 at 02:23:00PM -0700, Stephen Hurd wrote: > >> > The bnxt poll mode library (librte_pmd_bnxt) implements support fo= r > >> > Broadcom NetXtreme C-Series. These adapters support Standards- > >> > compliant 10/25/50Gbps 30MPPS full-duplex throughput. > >> > > >> > Information about this family of adapters can be found in the > >> > NetXtreme Brand section https://goo.gl/4H7q63 of the Broadcom web > >> > site http://www.broadcom.com/ > >> > > >> > With the current driver, allocated mbufs must be large enough to h= old > >> > the entire received frame. If the mbufs are not large enough, the > >> > packets will be dropped. This is most limiting when jumbo frames = are > >> > used. > >> > > >> > >> Applied to dpdk-next-net/rel_16_07 > >> > >> On apply I got conflicts with the nic overview document, so please c= heck > >> the > >> resulting information in that document is correct in the next-net tr= ee. > >> I also added a very short entry to the release notes for this new dr= iver > >> as > >> part of patch 1, since that was missing. Please also check that for > >> correctness > >> and send on any additional comments/corrections you want on that. > >> > > Thanks Bruce. I had a cursory glance =E2=80=8Band it looked good. > > We will update the > > =E2=80=8Bm=E2=80=8B further > > if necessary. > > =E2=80=8B > > > > > >> Thanks for all the work on this driver. > >> > >> Regards, > >> /Bruce > >> > > > >