7PM +0100, Loftus, Ciara wrote:
> >>>>
> >>>>
> >>>>> -Original Message- From: Stephen Hemminger
> >>>>> Sent: Monday 30 September 2019 18:12 To:
> >>>>> Loftus, Ciara Cc: dev@dpdk.org; Ye, Xiaolong
>
t;> -Original Message- From: Stephen Hemminger
>>>>> Sent: Monday 30 September 2019 18:12 To:
>>>>> Loftus, Ciara Cc: dev@dpdk.org; Ye, Xiaolong
>>>>> ; Laatz, Kevin ;
>>>>> Richardson, Bruce Subject: Re: [dpdk-dev]
>>>
t;>> Sent: Monday 30 September 2019 18:12 To:
> >>> Loftus, Ciara Cc: dev@dpdk.org; Ye, Xiaolong
> >>> ; Laatz, Kevin ;
> >>> Richardson, Bruce Subject: Re: [dpdk-dev]
> >>> [PATCH v2 2/3] net/af_xdp: support pinning of IRQs
> >>>
@dpdk.org; Ye, Xiaolong
>>> ; Laatz, Kevin ;
>>> Richardson, Bruce Subject: Re: [dpdk-dev]
>>> [PATCH v2 2/3] net/af_xdp: support pinning of IRQs
>>>
>>> On Mon, 30 Sep 2019 16:42:04 + Ciara Loftus
>>> wrote:
>>>
>>>>
Ok thanks
> -Original Message-
> From: Bruce Richardson
> Sent: Monday, October 21, 2019 7:26 PM
> To: Varghese, Vipin
> Cc: Loftus, Ciara ; 'Stephen Hemminger'
> ; 'dev@dpdk.org' ; Ye,
> Xiaolong ; Laatz, Kevin ;
> Yigit, Ferruh
> Su
On Mon, Oct 21, 2019 at 02:45:05PM +0100, Varghese, Vipin wrote:
> Hi Bruce,
>
> snipped
> > > This ability to have the driver pin the interrupts for the
> > > > user would be a big timesaver for developers too, who may be
> > > > constantly re- running apps when testing.
> > > Here my understand
Hi Bruce,
snipped
> > This ability to have the driver pin the interrupts for the
> > > user would be a big timesaver for developers too, who may be
> > > constantly re- running apps when testing.
> > Here my understanding, user can not or should not pass DPDK cores for
> interrupt pinning. So sho
On Mon, Oct 21, 2019 at 02:11:39PM +0100, Varghese, Vipin wrote:
> Hi Bruce,
>
> snipped
> > > >
> > > > For the no-pinning case, all IRQs are landing on the default core 0,
> > > > which results in very poor scaling versus the pinned case where scaling
> > > > is
> > linear.
> > >
> > > Thanks f
Hi Bruce,
snipped
> > >
> > > For the no-pinning case, all IRQs are landing on the default core 0,
> > > which results in very poor scaling versus the pinned case where scaling is
> linear.
> >
> > Thanks for the information, but a question here `Is the reason for
> > landing all IRQ on core '0' i
On Mon, Oct 21, 2019 at 01:52:27PM +0100, Varghese, Vipin wrote:
> Hi Ciara,
>
> snipped
> >
> > ifaces no pinning pinning
> > 1 9059100 9171612
> > 2 9261635 18376552
> > 3 9332804 27696702
> >
> > For the no-pinning case, all IRQs are landing on the default core
Hi Ciara,
snipped
>
> ifaces no pinning pinning
> 1 9059100 9171612
> 2 9261635 18376552
> 3 9332804 27696702
>
> For the no-pinning case, all IRQs are landing on the default core 0, which
> results in very poor scaling versus the pinned case where scaling is line
> > On Mon, 30 Sep 2019 16:42:04 +
> > Ciara Loftus wrote:
> >
> > > +/* drivers supported for the queue_irq option */
> > > +enum supported_drivers {
> > > + I40E_DRIVER,
> > > + IXGBE_DRIVER,
> > > + MLX5_DRIVER,
> > > + NUM_DRIVERS
> > > +};
> >
> > Anything device specific like this raises
On 09/30, Ciara Loftus wrote:
>Network devices using the AF_XDP PMD will trigger interrupts
>on reception of packets. The new PMD argument 'queue_irq'
>allows the user to specify a core on which to pin interrupts
>for a given queue. Multiple queue_irq arguments can be specified.
>For example:
>
>
On 03/10/2019 14:23, Loftus, Ciara wrote:
>
>
>> -Original Message-
>> From: Stephen Hemminger
>> Sent: Monday 30 September 2019 18:12
>> To: Loftus, Ciara
>> Cc: dev@dpdk.org; Ye, Xiaolong ; Laatz, Kevin
>> ; Richardson, Bruce
>> S
Subject: Re: [dpdk-dev]
> > [PATCH v2 2/3] net/af_xdp: support pinning of IRQs
> >
> > On Mon, 30 Sep 2019 16:42:04 + Ciara Loftus
> > wrote:
> >
> > > +/* drivers supported for the queue_irq option */ +enum
> > > supported
> -Original Message-
> From: Stephen Hemminger
> Sent: Monday 30 September 2019 18:12
> To: Loftus, Ciara
> Cc: dev@dpdk.org; Ye, Xiaolong ; Laatz, Kevin
> ; Richardson, Bruce
> Subject: Re: [dpdk-dev] [PATCH v2 2/3] net/af_xdp: support pinning of IRQs
>
>
On Mon, 30 Sep 2019 16:42:04 +
Ciara Loftus wrote:
> +/* drivers supported for the queue_irq option */
> +enum supported_drivers {
> + I40E_DRIVER,
> + IXGBE_DRIVER,
> + MLX5_DRIVER,
> + NUM_DRIVERS
> +};
Anything device specific like this raises a red flag to me.
This regex
Network devices using the AF_XDP PMD will trigger interrupts
on reception of packets. The new PMD argument 'queue_irq'
allows the user to specify a core on which to pin interrupts
for a given queue. Multiple queue_irq arguments can be specified.
For example:
--vdev=net_af_xdp1,iface=eth0,queue_c
18 matches
Mail list logo
