On 22.08.2019 19:07, William Tu wrote:
> On Thu, Aug 22, 2019 at 1:17 AM Ilya Maximets wrote:
>>
>> On 22.08.2019 0:38, William Tu wrote:
>>> On Wed, Aug 21, 2019 at 9:57 AM Alexander Duyck
>>> wrote:
On Wed, Aug 21, 2019 at 9:22 AM Ilya Maximets
wrote:
>
> On 21.08.2019
On Thu, Aug 22, 2019 at 1:17 AM Ilya Maximets wrote:
>
> On 22.08.2019 0:38, William Tu wrote:
> > On Wed, Aug 21, 2019 at 9:57 AM Alexander Duyck
> > wrote:
> >>
> >> On Wed, Aug 21, 2019 at 9:22 AM Ilya Maximets
> >> wrote:
> >>>
> >>> On 21.08.2019 4:17, Alexander Duyck wrote:
> On
On 22.08.2019 0:38, William Tu wrote:
> On Wed, Aug 21, 2019 at 9:57 AM Alexander Duyck
> wrote:
>>
>> On Wed, Aug 21, 2019 at 9:22 AM Ilya Maximets wrote:
>>>
>>> On 21.08.2019 4:17, Alexander Duyck wrote:
On Tue, Aug 20, 2019 at 8:58 AM Ilya Maximets
wrote:
>
> On
On 22.08.2019 10:12, Björn Töpel wrote:
> On Wed, 21 Aug 2019 at 18:57, Alexander Duyck
> wrote:
>>
>> On Wed, Aug 21, 2019 at 9:22 AM Ilya Maximets wrote:
>>>
>>> On 21.08.2019 4:17, Alexander Duyck wrote:
On Tue, Aug 20, 2019 at 8:58 AM Ilya Maximets
wrote:
>
> On
On Wed, 21 Aug 2019 at 18:57, Alexander Duyck wrote:
>
> On Wed, Aug 21, 2019 at 9:22 AM Ilya Maximets wrote:
> >
> > On 21.08.2019 4:17, Alexander Duyck wrote:
> > > On Tue, Aug 20, 2019 at 8:58 AM Ilya Maximets
> > > wrote:
> > >>
> > >> On 20.08.2019 18:35, Alexander Duyck wrote:
> > >>> On
On Wed, 21 Aug 2019 at 18:22, Ilya Maximets wrote:
>
> On 21.08.2019 4:17, Alexander Duyck wrote:
> > On Tue, Aug 20, 2019 at 8:58 AM Ilya Maximets
> > wrote:
> >>
> >> On 20.08.2019 18:35, Alexander Duyck wrote:
[...]
> >
> > So is it always in the same NAPI context?. I forgot, I was thinking
On Wed, Aug 21, 2019 at 9:57 AM Alexander Duyck
wrote:
>
> On Wed, Aug 21, 2019 at 9:22 AM Ilya Maximets wrote:
> >
> > On 21.08.2019 4:17, Alexander Duyck wrote:
> > > On Tue, Aug 20, 2019 at 8:58 AM Ilya Maximets
> > > wrote:
> > >>
> > >> On 20.08.2019 18:35, Alexander Duyck wrote:
> > >>>
On Wed, Aug 21, 2019 at 9:22 AM Ilya Maximets wrote:
>
> On 21.08.2019 4:17, Alexander Duyck wrote:
> > On Tue, Aug 20, 2019 at 8:58 AM Ilya Maximets
> > wrote:
> >>
> >> On 20.08.2019 18:35, Alexander Duyck wrote:
> >>> On Tue, Aug 20, 2019 at 8:18 AM Ilya Maximets
> >>> wrote:
>
>
On 21.08.2019 4:17, Alexander Duyck wrote:
> On Tue, Aug 20, 2019 at 8:58 AM Ilya Maximets wrote:
>>
>> On 20.08.2019 18:35, Alexander Duyck wrote:
>>> On Tue, Aug 20, 2019 at 8:18 AM Ilya Maximets
>>> wrote:
Tx code doesn't clear the descriptor status after cleaning.
So, if the
On 20 Aug 2019, at 17:16, Ilya Maximets wrote:
Tx code doesn't clear the descriptor status after cleaning.
So, if the budget is larger than number of used elems in a ring, some
descriptors will be accounted twice and xsk_umem_complete_tx will move
prod_tail far beyond the prod_head breaking
On Tue, Aug 20, 2019 at 8:58 AM Ilya Maximets wrote:
>
> On 20.08.2019 18:35, Alexander Duyck wrote:
> > On Tue, Aug 20, 2019 at 8:18 AM Ilya Maximets
> > wrote:
> >>
> >> Tx code doesn't clear the descriptor status after cleaning.
> >> So, if the budget is larger than number of used elems in a
On 20.08.2019 18:35, Alexander Duyck wrote:
> On Tue, Aug 20, 2019 at 8:18 AM Ilya Maximets wrote:
>>
>> Tx code doesn't clear the descriptor status after cleaning.
>> So, if the budget is larger than number of used elems in a ring, some
>> descriptors will be accounted twice and
On Tue, Aug 20, 2019 at 8:18 AM Ilya Maximets wrote:
>
> Tx code doesn't clear the descriptor status after cleaning.
> So, if the budget is larger than number of used elems in a ring, some
> descriptors will be accounted twice and xsk_umem_complete_tx will move
> prod_tail far beyond the
Tx code doesn't clear the descriptor status after cleaning.
So, if the budget is larger than number of used elems in a ring, some
descriptors will be accounted twice and xsk_umem_complete_tx will move
prod_tail far beyond the prod_head breaking the comletion queue ring.
Fix that by limiting the
14 matches
Mail list logo