From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jan Blunck <jblunck@infradead.org>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, i.maximets@samsung.com,
bruce.richardson@intel.com, declan.doherty@intel.com,
ehkinzie@gmail.com, bernard.iremonger@intel.com, stable@dpdk.org
Subject: Re: [PATCH v2 0/5] bonding: setup all queues of slave devices
Date: Wed, 21 Dec 2016 18:48:48 +0100 [thread overview]
Message-ID: <2622375.75ISYoc1AV@xps13> (raw)
In-Reply-To: <1479986809-14934-1-git-send-email-jblunck@infradead.org>
2016-11-24 12:26, Jan Blunck:
> Prior to 16.11 some drivers (e.g. virtio) still had problems if their
> queues where setup repeatedly. The bonding driver was working around the
> problem by reusing already setup queues. This series of patches changes the
> way how queue setup is done to give control to the driver to properly release
> already initialized queues before they are setup again. Therefore the driver
> call sequence is as if the number of queues is temporarily reduced before the
> queues are setup again.
>
> Ilya Maximets (1):
> Revert "bonding: use existing enslaved device queues"
>
> Jan Blunck (4):
> ethdev: Call rx/tx_queue_release before rx/tx_queue_setup
> ethdev: Free rx/tx_queues after releasing all queues
> ethdev: Add DPDK internal _rte_eth_dev_reset()
> net/bonding: Force reconfiguration of removed slave interfaces
Applied, thanks
prev parent reply other threads:[~2016-12-21 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 11:26 [PATCH v2 0/5] bonding: setup all queues of slave devices Jan Blunck
2016-11-24 11:26 ` [PATCH v2 1/5] ethdev: Call rx/tx_queue_release before rx/tx_queue_setup Jan Blunck
2016-11-24 11:26 ` [PATCH v2 2/5] ethdev: Free rx/tx_queues after releasing all queues Jan Blunck
2016-11-24 11:26 ` [PATCH v2 3/5] ethdev: Add DPDK internal _rte_eth_dev_reset() Jan Blunck
2016-11-24 11:26 ` [PATCH v2 4/5] net/bonding: Force reconfiguration of removed slave interfaces Jan Blunck
2016-11-24 11:26 ` [PATCH v2 5/5] Revert "bonding: use existing enslaved device queues" Jan Blunck
2016-12-21 17:48 ` Thomas Monjalon [this message]
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=2622375.75ISYoc1AV@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bernard.iremonger@intel.com \
--cc=bruce.richardson@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ehkinzie@gmail.com \
--cc=ferruh.yigit@intel.com \
--cc=i.maximets@samsung.com \
--cc=jblunck@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.