Re: [PATCH v2 0/7] net: mvneta: Switch to per-CPU irq and make rxq_def useful

On Wed, 30 Sep 2015, David Miller wrote: > From: Thomas Gleixner > Date: Wed, 30 Sep 2015 16:56:06 +0200 (CEST) > > > On Tue, 29 Sep 2015, David Miller wrote: > >> From: Gregory CLEMENT > >> Date: Fri, 25 Sep 2015 18:09:31 +0200 > >> > >> > As stated in the first version: "this patchset

Re: [PATCH v2 0/7] net: mvneta: Switch to per-CPU irq and make rxq_def useful

From: Thomas Gleixner Date: Wed, 30 Sep 2015 16:56:06 +0200 (CEST) > On Tue, 29 Sep 2015, David Miller wrote: >> From: Gregory CLEMENT >> Date: Fri, 25 Sep 2015 18:09:31 +0200 >> >> > As stated in the first version: "this patchset reworks the Marvell >> > neta driver in order to really support

Re: [PATCH v2 0/7] net: mvneta: Switch to per-CPU irq and make rxq_def useful

On Tue, 29 Sep 2015, David Miller wrote: > From: Gregory CLEMENT > Date: Fri, 25 Sep 2015 18:09:31 +0200 > > > As stated in the first version: "this patchset reworks the Marvell > > neta driver in order to really support its per-CPU interrupts, instead > > of faking them as SPI, and allow the

Re: [PATCH v2 0/7] net: mvneta: Switch to per-CPU irq and make rxq_def useful

On Fri, 25 Sep 2015, Gregory CLEMENT wrote: > I also reorganized the series, the 3 first patches should go through > the irq subsystem, whereas the 4 others should go to the network > subsystem. > > However, there is a runtime dependency between the two parts. Patch 5 > depend on the patch 3 to

Re: [PATCH v2 0/7] net: mvneta: Switch to per-CPU irq and make rxq_def useful

On Wed, 30 Sep 2015, David Miller wrote: > From: Thomas Gleixner > Date: Wed, 30 Sep 2015 16:56:06 +0200 (CEST) > > > On Tue, 29 Sep 2015, David Miller wrote: > >> From: Gregory CLEMENT > >> Date: Fri, 25 Sep 2015 18:09:31 +0200 > >> > >>

Re: [PATCH v2 0/7] net: mvneta: Switch to per-CPU irq and make rxq_def useful

On Fri, 25 Sep 2015, Gregory CLEMENT wrote: > I also reorganized the series, the 3 first patches should go through > the irq subsystem, whereas the 4 others should go to the network > subsystem. > > However, there is a runtime dependency between the two parts. Patch 5 > depend on the patch 3 to

Re: [PATCH v2 0/7] net: mvneta: Switch to per-CPU irq and make rxq_def useful

On Tue, 29 Sep 2015, David Miller wrote: > From: Gregory CLEMENT > Date: Fri, 25 Sep 2015 18:09:31 +0200 > > > As stated in the first version: "this patchset reworks the Marvell > > neta driver in order to really support its per-CPU interrupts, instead > > of

Re: [PATCH v2 0/7] net: mvneta: Switch to per-CPU irq and make rxq_def useful

From: Thomas Gleixner Date: Wed, 30 Sep 2015 16:56:06 +0200 (CEST) > On Tue, 29 Sep 2015, David Miller wrote: >> From: Gregory CLEMENT >> Date: Fri, 25 Sep 2015 18:09:31 +0200 >> >> > As stated in the first version: "this patchset reworks

Re: [PATCH v2 0/7] net: mvneta: Switch to per-CPU irq and make rxq_def useful

From: Gregory CLEMENT Date: Fri, 25 Sep 2015 18:09:31 +0200 > As stated in the first version: "this patchset reworks the Marvell > neta driver in order to really support its per-CPU interrupts, instead > of faking them as SPI, and allow the use of any RX queue instead of > the hardcoded RX queue

Re: [PATCH v2 0/7] net: mvneta: Switch to per-CPU irq and make rxq_def useful

From: Gregory CLEMENT Date: Fri, 25 Sep 2015 18:09:31 +0200 > As stated in the first version: "this patchset reworks the Marvell > neta driver in order to really support its per-CPU interrupts, instead > of faking them as SPI, and allow the use of any RX queue

[PATCH v2 0/7] net: mvneta: Switch to per-CPU irq and make rxq_def useful

Hi, As stated in the first version: "this patchset reworks the Marvell neta driver in order to really support its per-CPU interrupts, instead of faking them as SPI, and allow the use of any RX queue instead of the hardcoded RX queue 0 that we have currently." Following the review which has been

[PATCH v2 0/7] net: mvneta: Switch to per-CPU irq and make rxq_def useful

Hi, As stated in the first version: "this patchset reworks the Marvell neta driver in order to really support its per-CPU interrupts, instead of faking them as SPI, and allow the use of any RX queue instead of the hardcoded RX queue 0 that we have currently." Following the review which has been