[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-11-11 Thread Ilya Maximets
Ping. On 28.10.2016 09:14, Ilya Maximets wrote: > On 25.10.2016 09:26, Ilya Maximets wrote: >> On 24.10.2016 17:54, Jan Blunck wrote: >>> On Wed, Oct 19, 2016 at 5:47 AM, Ilya Maximets >>> wrote: On 18.10.2016 18:19, Jan Blunck wrote: > On Tue, Oct 18, 2016 at 2:49 PM, Ilya Maximets

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-28 Thread Ilya Maximets
On 25.10.2016 09:26, Ilya Maximets wrote: > On 24.10.2016 17:54, Jan Blunck wrote: >> On Wed, Oct 19, 2016 at 5:47 AM, Ilya Maximets >> wrote: >>> On 18.10.2016 18:19, Jan Blunck wrote: On Tue, Oct 18, 2016 at 2:49 PM, Ilya Maximets wrote: > On 18.10.2016 15:28, Jan Blunck wrote:

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-25 Thread Bruce Richardson
On Tue, Oct 25, 2016 at 02:48:04PM +0100, Declan Doherty wrote: > On 25/10/16 13:57, Bruce Richardson wrote: > > On Mon, Oct 24, 2016 at 04:07:17PM +0100, Declan Doherty wrote: > > > On 24/10/16 15:51, Jan Blunck wrote: > > > > On Mon, Oct 24, 2016 at 7:02 AM, Declan Doherty > > > > wrote: > > >

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-25 Thread Bruce Richardson
On Wed, Oct 19, 2016 at 10:55:25AM +0100, Bruce Richardson wrote: > On Thu, Oct 06, 2016 at 03:32:36PM +0100, Declan Doherty wrote: > > On 07/09/16 13:28, Ilya Maximets wrote: > > > This reverts commit 5b7bb2bda5519b7800f814df64d4e015282140e5. > > > > > > It is necessary to reconfigure all queues

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-25 Thread Declan Doherty
On 25/10/16 13:57, Bruce Richardson wrote: > On Mon, Oct 24, 2016 at 04:07:17PM +0100, Declan Doherty wrote: >> On 24/10/16 15:51, Jan Blunck wrote: >>> On Mon, Oct 24, 2016 at 7:02 AM, Declan Doherty >>> wrote: On 14/10/16 00:37, Eric Kinzie wrote: > > On Wed Oct 12 16:24:21 +0100

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-25 Thread Ilya Maximets
On 24.10.2016 17:54, Jan Blunck wrote: > On Wed, Oct 19, 2016 at 5:47 AM, Ilya Maximets > wrote: >> On 18.10.2016 18:19, Jan Blunck wrote: >>> On Tue, Oct 18, 2016 at 2:49 PM, Ilya Maximets >>> wrote: On 18.10.2016 15:28, Jan Blunck wrote: > If the application already configured

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-24 Thread Declan Doherty
On 24/10/16 15:51, Jan Blunck wrote: > On Mon, Oct 24, 2016 at 7:02 AM, Declan Doherty > wrote: >> On 14/10/16 00:37, Eric Kinzie wrote: >>> >>> On Wed Oct 12 16:24:21 +0100 2016, Bruce Richardson wrote: On Wed, Oct 12, 2016 at 04:24:54PM +0300, Ilya Maximets wrote: > > On

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-24 Thread Declan Doherty
On 14/10/16 00:37, Eric Kinzie wrote: > On Wed Oct 12 16:24:21 +0100 2016, Bruce Richardson wrote: >> On Wed, Oct 12, 2016 at 04:24:54PM +0300, Ilya Maximets wrote: >>> On 07.10.2016 05:02, Eric Kinzie wrote: On Wed Sep 07 15:28:10 +0300 2016, Ilya Maximets wrote: > This reverts commit

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-24 Thread Jan Blunck
On Wed, Oct 19, 2016 at 5:47 AM, Ilya Maximets wrote: > On 18.10.2016 18:19, Jan Blunck wrote: >> On Tue, Oct 18, 2016 at 2:49 PM, Ilya Maximets >> wrote: >>> On 18.10.2016 15:28, Jan Blunck wrote: If the application already configured queues the PMD should not silently claim

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-24 Thread Jan Blunck
On Mon, Oct 24, 2016 at 7:02 AM, Declan Doherty wrote: > On 14/10/16 00:37, Eric Kinzie wrote: >> >> On Wed Oct 12 16:24:21 +0100 2016, Bruce Richardson wrote: >>> >>> On Wed, Oct 12, 2016 at 04:24:54PM +0300, Ilya Maximets wrote: On 07.10.2016 05:02, Eric Kinzie wrote: > > On

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-19 Thread Ilya Maximets
On 18.10.2016 18:19, Jan Blunck wrote: > On Tue, Oct 18, 2016 at 2:49 PM, Ilya Maximets > wrote: >> On 18.10.2016 15:28, Jan Blunck wrote: >>> If the application already configured queues the PMD should not >>> silently claim ownership and reset them. >>> >>> What exactly is the problem when

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-19 Thread Bruce Richardson
On Thu, Oct 06, 2016 at 03:32:36PM +0100, Declan Doherty wrote: > On 07/09/16 13:28, Ilya Maximets wrote: > > This reverts commit 5b7bb2bda5519b7800f814df64d4e015282140e5. > > > > It is necessary to reconfigure all queues every time because configuration > > can be changed. > > > > Hey Ilya,

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-18 Thread Jan Blunck
On Tue, Oct 18, 2016 at 2:49 PM, Ilya Maximets wrote: > On 18.10.2016 15:28, Jan Blunck wrote: >> If the application already configured queues the PMD should not >> silently claim ownership and reset them. >> >> What exactly is the problem when changing MTU? This works fine from >> what I can

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-18 Thread Ilya Maximets
On 18.10.2016 15:28, Jan Blunck wrote: > If the application already configured queues the PMD should not > silently claim ownership and reset them. > > What exactly is the problem when changing MTU? This works fine from > what I can tell. Following scenario leads to APP PANIC: 1.

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-18 Thread Jan Blunck
If the application already configured queues the PMD should not silently claim ownership and reset them. What exactly is the problem when changing MTU? This works fine from what I can tell. Cheers, Jan On Wed, Sep 7, 2016 at 2:28 PM, Ilya Maximets wrote: > This reverts commit

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-13 Thread Eric Kinzie
On Wed Oct 12 16:24:21 +0100 2016, Bruce Richardson wrote: > On Wed, Oct 12, 2016 at 04:24:54PM +0300, Ilya Maximets wrote: > > On 07.10.2016 05:02, Eric Kinzie wrote: > > > On Wed Sep 07 15:28:10 +0300 2016, Ilya Maximets wrote: > > >> This reverts commit 5b7bb2bda5519b7800f814df64d4e015282140e5.

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-12 Thread Ilya Maximets
On 07.10.2016 05:02, Eric Kinzie wrote: > On Wed Sep 07 15:28:10 +0300 2016, Ilya Maximets wrote: >> This reverts commit 5b7bb2bda5519b7800f814df64d4e015282140e5. >> >> It is necessary to reconfigure all queues every time because configuration >> can be changed. >> >> For example, if we're

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-12 Thread Bruce Richardson
On Wed, Oct 12, 2016 at 04:24:54PM +0300, Ilya Maximets wrote: > On 07.10.2016 05:02, Eric Kinzie wrote: > > On Wed Sep 07 15:28:10 +0300 2016, Ilya Maximets wrote: > >> This reverts commit 5b7bb2bda5519b7800f814df64d4e015282140e5. > >> > >> It is necessary to reconfigure all queues every time

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-06 Thread Eric Kinzie
On Wed Sep 07 15:28:10 +0300 2016, Ilya Maximets wrote: > This reverts commit 5b7bb2bda5519b7800f814df64d4e015282140e5. > > It is necessary to reconfigure all queues every time because configuration > can be changed. > > For example, if we're reconfiguring bonding device with new memory pool, >

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-10-06 Thread Declan Doherty
On 07/09/16 13:28, Ilya Maximets wrote: > This reverts commit 5b7bb2bda5519b7800f814df64d4e015282140e5. > > It is necessary to reconfigure all queues every time because configuration > can be changed. > Hey Ilya, this makes sense. I guess this was my original intention but I missed this case in

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-09-16 Thread Ilya Maximets
Ping. Best regards, Ilya Maximets. On 07.09.2016 15:28, Ilya Maximets wrote: > This reverts commit 5b7bb2bda5519b7800f814df64d4e015282140e5. > > It is necessary to reconfigure all queues every time because configuration > can be changed. > > For example, if we're reconfiguring bonding device

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

2016-09-07 Thread Ilya Maximets
This reverts commit 5b7bb2bda5519b7800f814df64d4e015282140e5. It is necessary to reconfigure all queues every time because configuration can be changed. For example, if we're reconfiguring bonding device with new memory pool, already configured queues will still use the old one. And if the old