DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@6wind.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] eal / bonding pmd cleanup
Date: Tue, 16 Sep 2014 15:05:11 +0200	[thread overview]
Message-ID: <CALwxeUvNG_nzCBESYpSg3SxJqDBdWOMeuAZNbMB-L14ZugD31A@mail.gmail.com> (raw)
In-Reply-To: <1409062338-26477-1-git-send-email-david.marchand@6wind.com>

On Tue, Aug 26, 2014 at 4:12 PM, David Marchand <david.marchand@6wind.com>
wrote:

> This patchset reworks the bonding pmd so that we don't need to modify the
> eal
> for this pmd to work.
>
> Basically, the arguments parsed at bond_init are stored in the bond private
> structure to be used at dev_configure time.
> If no argument are present, we suppose that the bonding api has been
> called.
>

I did not get any comment on these patches.
Anyone ?

The idea here is to keep pmd stuff in the pmds and avoid polluting the eal.


-- 
David Marchand

  parent reply	other threads:[~2014-09-16 12:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 14:12 David Marchand
2014-08-26 14:12 ` [dpdk-dev] [PATCH 1/3] bond: move param parsing in dev_configure David Marchand
2014-08-26 14:12 ` [dpdk-dev] [PATCH 2/3] Revert "eal: support link bonding device initialization" David Marchand
2014-08-26 14:12 ` [dpdk-dev] [PATCH 3/3] eal: probe pci devices at rte_eal_init time David Marchand
2014-09-16 13:05 ` David Marchand [this message]
2014-09-22 11:02   ` [dpdk-dev] [PATCH 0/3] eal / bonding pmd cleanup David Marchand
2014-09-22 13:04     ` Neil Horman
2014-09-29 12:12       ` Thomas Monjalon

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=CALwxeUvNG_nzCBESYpSg3SxJqDBdWOMeuAZNbMB-L14ZugD31A@mail.gmail.com \
    --to=david.marchand@6wind.com \
    --cc=dev@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).