>>> ; Reshma Pattan
> >>>>
> >>>> Subject: Re: Issues around packet capture when secondary process is
> >>>> doing rx/tx
> >>>>
> >>>> On Mon, 8 Jan 2024 15:13:25 +
> >>>> Konstantin An
> Maybe pdump needs to have its own socket and control thread?
> Or MP socket needs to have some multicast fanout to all secondaries?
> >>>
> >>> Might be we can do something simpler: pass to pdump_enable(), where we
> >>> want to enable it:
> >>> on primary (remote_ process or secon
l.com; Gowda, Sandesh
>>>> ; Reshma Pattan
>>>>
>>>> Subject: Re: Issues around packet capture when secondary process is doing
>>>> rx/tx
>>>>
>>>> On Mon, 8 Jan 2024 15:13:25 +
>>>> Konstantin Ananyev
> >> -Original Message-
> >> From: Stephen Hemminger
> >> Sent: Tuesday, January 9, 2024 11:07 PM
> >> To: Konstantin Ananyev
> >> Cc: dev@dpdk.org; arshdeep.k...@intel.com; Gowda, Sandesh
> >> ; Reshma Pattan
> >>
> &
a Pattan
>>
>> Subject: Re: Issues around packet capture when secondary process is doing
>> rx/tx
>>
>> On Mon, 8 Jan 2024 15:13:25 +
>> Konstantin Ananyev wrote:
>>
>>>> I have been looking at a problem reported by Sandesh
>>>&
On 1/9/2024 11:07 PM, Stephen Hemminger wrote:
> On Tue, 9 Jan 2024 15:06:47 -0800
> Stephen Hemminger wrote:
>
>> On Mon, 8 Jan 2024 15:13:25 +
>> Konstantin Ananyev wrote:
>>
I have been looking at a problem reported by Sandesh
where packet capture does not work if rx/tx burst is
On 1/8/2024 10:41 AM, Morten Brørup wrote:
>> From: Stephen Hemminger [mailto:step...@networkplumber.org]
>> Sent: Monday, 8 January 2024 02.59
>>
>> I have been looking at a problem reported by Sandesh
>> where packet capture does not work if rx/tx burst is done in secondary
>> process.
>>
>> The
On 1/8/2024 3:13 PM, Konstantin Ananyev wrote:
>
>
>> I have been looking at a problem reported by Sandesh
>> where packet capture does not work if rx/tx burst is done in secondary
>> process.
>>
>> The root cause is that existing rx/tx callback model just doesn't work
>> unless the process doin
On Mon, 8 Jan 2024 15:13:25 +
Konstantin Ananyev wrote:
> > I have been looking at a problem reported by Sandesh
> > where packet capture does not work if rx/tx burst is done in secondary
> > process.
> >
> > The root cause is that existing rx/tx callback model just doesn't work
> > unless
> -Original Message-
> From: Stephen Hemminger
> Sent: Tuesday, January 9, 2024 11:07 PM
> To: Konstantin Ananyev
> Cc: dev@dpdk.org; arshdeep.k...@intel.com; Gowda, Sandesh
> ; Reshma Pattan
>
> Subject: Re: Issues around packet capture when secondary p
On Mon, 8 Jan 2024 15:13:25 +
Konstantin Ananyev wrote:
> > I have been looking at a problem reported by Sandesh
> > where packet capture does not work if rx/tx burst is done in secondary
> > process.
> >
> > The root cause is that existing rx/tx callback model just doesn't work
> > unless
On Tue, 9 Jan 2024 15:06:47 -0800
Stephen Hemminger wrote:
> On Mon, 8 Jan 2024 15:13:25 +
> Konstantin Ananyev wrote:
>
> > > I have been looking at a problem reported by Sandesh
> > > where packet capture does not work if rx/tx burst is done in secondary
> > > process.
> > >
> > > The r
> -Original Message-
> From: Stephen Hemminger
> Sent: Sunday, January 7, 2024 7:59 PM
> To: dev@dpdk.org
> Cc: arshdeep.k...@intel.com; Gowda, Sandesh ;
> Reshma Pattan
> Subject: Issues around packet capture when secondary process is doing rx/tx
>
> I hav
On Mon, 8 Jan 2024 15:13:25 +
Konstantin Ananyev wrote:
> > I have been looking at a problem reported by Sandesh
> > where packet capture does not work if rx/tx burst is done in secondary
> > process.
> >
> > The root cause is that existing rx/tx callback model just doesn't work
> > unless
> I have been looking at a problem reported by Sandesh
> where packet capture does not work if rx/tx burst is done in secondary
> process.
>
> The root cause is that existing rx/tx callback model just doesn't work
> unless the process doing the rx/tx burst calls is the same one that
> register
> From: Stephen Hemminger [mailto:step...@networkplumber.org]
> Sent: Monday, 8 January 2024 02.59
>
> I have been looking at a problem reported by Sandesh
> where packet capture does not work if rx/tx burst is done in secondary
> process.
>
> The root cause is that existing rx/tx callback model
16 matches
Mail list logo
