DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahed Shaikh <shshaikh@marvell.com>
To: Jerin Jacob <jerinjacobk@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Rasesh Mody <rmody@marvell.com>,
	"Jerin Jacob Kollanukkaran" <jerinj@marvell.com>,
	GR-Everest-DPDK-Dev <GR-Everest-DPDK-Dev@marvell.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1 1/5] net/qede: refactor Rx and Tx queue	setup
Date: Thu, 12 Sep 2019 14:48:14 +0000	[thread overview]
Message-ID: <BYAPR18MB26960319D441C84724FE3C4AD3B00@BYAPR18MB2696.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CALBAE1OfpnkWPpjLyCe76AohvX-6Dm9-ek=kANxKSEH_SJNE-w@mail.gmail.com>

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Jerin Jacob
> Sent: Thursday, September 12, 2019 6:04 PM
> To: Shahed Shaikh <shshaikh@marvell.com>
> Cc: dev@dpdk.org; Rasesh Mody <rmody@marvell.com>; Jerin Jacob
> Kollanukkaran <jerinj@marvell.com>; GR-Everest-DPDK-Dev <GR-Everest-DPDK-
> Dev@marvell.com>; stable@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v1 1/5] net/qede: refactor Rx and Tx queue
> setup
> 
> On Fri, Sep 6, 2019 at 1:10 PM Shahed Shaikh <shshaikh@marvell.com> wrote:
> >
> > This patch refactors Rx and Tx queue setup flow required to allow odd
> > number of queues to be configured in next patch.
> >
> > This is the first patch of the series required to fix an issue where
> > qede port initialization in ovs-dpdk fails due to 1 Rx/Tx queue
> > configuration. Detailed explaination is given in next patch.
> >
> > Fixes: 2af14ca79c0a ("net/qede: support 100G")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Shahed Shaikh <shshaikh@marvell.com>
> > ---
> 
> This series looks good to me.
> Looks like there is genuine compilation issue from qede driver.
> http://mails.dpdk.org/archives/test-report/2019-September/096256.html
> 
> Please confirm in either case.
Hi Jerin,
Sending v2 to fix compilation failure for clang compiler reported here -
http://mails.dpdk.org/archives/test-report/2019-September/096256.html

Thanks,
Shahed

  reply	other threads:[~2019-09-12 14:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06  7:32 [dpdk-dev] [PATCH v1 0/5] net/qede: fixes and enhancement Shahed Shaikh
2019-09-06  7:32 ` [dpdk-dev] [PATCH v1 1/5] net/qede: refactor Rx and Tx queue setup Shahed Shaikh
2019-09-12 12:34   ` Jerin Jacob
2019-09-12 14:48     ` Shahed Shaikh [this message]
2019-09-06  7:32 ` [dpdk-dev] [PATCH v1 2/5] net/qede: fix ovs-dpdk failure when using odd number of queues on 100Gb mode Shahed Shaikh
2019-09-06  7:32 ` [dpdk-dev] [PATCH v1 3/5] net/qede: fix RSS configuration as per new 100Gb queue allocation method Shahed Shaikh
2019-09-06  7:32 ` [dpdk-dev] [PATCH v1 4/5] net/qede: fix stats flow " Shahed Shaikh
2019-09-06  7:32 ` [dpdk-dev] [PATCH v1 5/5] net/qede: implement rte_flow drop action Shahed Shaikh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BYAPR18MB26960319D441C84724FE3C4AD3B00@BYAPR18MB2696.namprd18.prod.outlook.com \
    --to=shshaikh@marvell.com \
    --cc=GR-Everest-DPDK-Dev@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=jerinjacobk@gmail.com \
    --cc=rmody@marvell.com \
    --cc=stable@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).