DPDK patches and discussions
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: David Marchand <david.marchand@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] eal / bonding pmd cleanup
Date: Mon, 22 Sep 2014 09:04:26 -0400
Message-ID: <20140922130426.GE25406@hmsreliant.think-freely.org> (raw)
In-Reply-To: <CALwxeUuhwaTz+WCa2B2_W52MPt8rvxC_ia8g-kZuJx+aV-8HxA@mail.gmail.com>

On Mon, Sep 22, 2014 at 01:02:08PM +0200, David Marchand wrote:
> On Tue, Sep 16, 2014 at 3:05 PM, David Marchand <david.marchand@6wind.com>
> wrote:
> 
> > 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.
> >
> 
> ping
Sorry, it was on my todo list and it kept getting pushed back.  I like the
change, its makes great sense and does proper isolation of the PMD.

Acked-by: Neil Horman <nhorman@tuxdriver.com>

> 
> 
> -- 
> David Marchand
> 

  reply	other threads:[~2014-09-22 12:58 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 ` [dpdk-dev] [PATCH 0/3] eal / bonding pmd cleanup David Marchand
2014-09-22 11:02   ` David Marchand
2014-09-22 13:04     ` Neil Horman [this message]
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=20140922130426.GE25406@hmsreliant.think-freely.org \
    --to=nhorman@tuxdriver.com \
    --cc=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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git