From: Krzysztof Kanas <kkanas@marvell.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Krzysztof Kanas <kkanas@marvell.com>, dev <dev@dpdk.org>,
Chas Williams <chas3@att.com>,
"danielx.t.mrzyglod@intel.com" <danielx.t.mrzyglod@intel.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH 1/2] net/bonding: fix stack overflow in selection logic
Date: Wed, 7 Aug 2019 07:41:00 +0000 [thread overview]
Message-ID: <20190807073945.GA15490@idea320s> (raw)
In-Reply-To: <CAJFAV8yByBhs6u4jQED-AoRxrkcx_qcDdMYL1G06M1+u8uR68A@mail.gmail.com>
On 19-08-05 17:09, David Marchand wrote:
> External Email
>
> ----------------------------------------------------------------------
> On Mon, Aug 5, 2019 at 4:46 PM <kkanas@marvell.com> wrote:
> >
> > From: Krzysztof Kanas <kkanas@marvell.com>
> >
> > Bonding selection logic uses agg_bandwidth, agg_count indexed by port_id
> > but those arrays are 8 entries long.
>
> Idem http://mails.dpdk.org/archives/dev/2019-July/140020.html
>
> I did not get a reply from you.
>
Sorry I have look at mailing list and looked that discussion stooped at
http://mails.dpdk.org/archives/dev/2019-March/127444.html
So I prepared fix for and wanted to reply to that thread with new
patches.
Unfortunately I added '--reply-to' to git send-email command and not
--in-reply-to as I should have done.
>
> --
> David Marchand
next prev parent reply other threads:[~2019-08-07 7:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 14:44 [dpdk-dev] " kkanas
2019-08-05 14:44 ` [dpdk-dev] [PATCH 2/2] net/bonding: fix " kkanas
2019-10-08 14:34 ` Yigit, Ferruh
2019-10-10 8:27 ` [dpdk-dev] [PATCH v2] " kkanas
2019-10-10 13:30 ` Chas Williams
2019-10-11 6:34 ` [dpdk-dev] [PATCH v3] " kkanas
2019-10-11 15:38 ` Chas Williams
2019-11-13 8:22 ` [dpdk-dev] [PATCH v4] " kkanas
2019-11-15 15:56 ` Ferruh Yigit
2019-08-05 15:09 ` [dpdk-dev] [PATCH 1/2] net/bonding: fix stack overflow in " David Marchand
2019-08-07 7:41 ` Krzysztof Kanas [this message]
2019-10-08 14:33 ` Yigit, Ferruh
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=20190807073945.GA15490@idea320s \
--to=kkanas@marvell.com \
--cc=chas3@att.com \
--cc=danielx.t.mrzyglod@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
/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).