Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Hi,
while XENO_OPT_DEBUG is generally a useful switch for tracing
potential
issues in the core and the skins, it also introduces high
latenc
Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Hi,
while XENO_OPT_DEBUG is generally a useful switch for tracing
potential
issues in the core and the skins, it also introduces high
latenc
Philippe Gerum wrote:
> Jan Kiszka wrote:
>> Philippe Gerum wrote:
>>
>>> Jan Kiszka wrote:
>>>
Philippe Gerum wrote:
> Jan Kiszka wrote:
>
>
>> Hi,
>>
>> while XENO_OPT_DEBUG is generally a useful switch for tracing
>> potential
>> issues in the core
Philippe Gerum wrote:
> Jan Kiszka wrote:
>> Philippe Gerum wrote:
>>
>>> Jan Kiszka wrote:
>>>
Philippe Gerum wrote:
> Jan Kiszka wrote:
>
>
>> Hi,
>>
>> while XENO_OPT_DEBUG is generally a useful switch for tracing
>> potential
>> issues in the core
Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Hi,
while XENO_OPT_DEBUG is generally a useful switch for tracing potential
issues in the core and the skins, it also introduces high latencies via
the queue debugging feature (due to chec
Philippe Gerum wrote:
> Jan Kiszka wrote:
>> Philippe Gerum wrote:
>>
>>> Jan Kiszka wrote:
>>>
Hi,
while XENO_OPT_DEBUG is generally a useful switch for tracing potential
issues in the core and the skins, it also introduces high latencies via
the queue debugging feature (d
Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Hi,
while XENO_OPT_DEBUG is generally a useful switch for tracing potential
issues in the core and the skins, it also introduces high latencies via
the queue debugging feature (due to chec
Philippe Gerum wrote:
> Jan Kiszka wrote:
>> Philippe Gerum wrote:
>>
>>> Jan Kiszka wrote:
>>>
Hi,
while XENO_OPT_DEBUG is generally a useful switch for tracing potential
issues in the core and the skins, it also introduces high latencies via
the queue debugging feature (d
Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Hi,
while XENO_OPT_DEBUG is generally a useful switch for tracing potential
issues in the core and the skins, it also introduces high latencies via
the queue debugging feature (due to checks iterating over whole queues).
This patch i
Philippe Gerum wrote:
> Jan Kiszka wrote:
>> Hi,
>>
>> while XENO_OPT_DEBUG is generally a useful switch for tracing potential
>> issues in the core and the skins, it also introduces high latencies via
>> the queue debugging feature (due to checks iterating over whole queues).
>>
>> This patch intr
Jan Kiszka wrote:
Hi,
while XENO_OPT_DEBUG is generally a useful switch for tracing potential
issues in the core and the skins, it also introduces high latencies via
the queue debugging feature (due to checks iterating over whole queues).
This patch introduces separate control over queue debugg
Jan Kiszka wrote:
> Jan Kiszka wrote:
> > Hi,
> >
> > while XENO_OPT_DEBUG is generally a useful switch for tracing potential
> > issues in the core and the skins, it also introduces high latencies via
> > the queue debugging feature (due to checks iterating over whole queues).
> >
> > Th
Jan Kiszka wrote:
> Hi,
>
> while XENO_OPT_DEBUG is generally a useful switch for tracing potential
> issues in the core and the skins, it also introduces high latencies via
> the queue debugging feature (due to checks iterating over whole queues).
>
> This patch introduces separate control over
Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Hi,
while XENO_OPT_DEBUG is generally a useful switch for tracing potential
issues in the core and the skins, it also introduces high latencies via
the queue debugging feature (due to checks iterating over whole queues).
This patch i
Philippe Gerum wrote:
> Jan Kiszka wrote:
>> Hi,
>>
>> while XENO_OPT_DEBUG is generally a useful switch for tracing potential
>> issues in the core and the skins, it also introduces high latencies via
>> the queue debugging feature (due to checks iterating over whole queues).
>>
>> This patch intr
Jan Kiszka wrote:
Hi,
while XENO_OPT_DEBUG is generally a useful switch for tracing potential
issues in the core and the skins, it also introduces high latencies via
the queue debugging feature (due to checks iterating over whole queues).
This patch introduces separate control over queue debugg
Jan Kiszka wrote:
> Jan Kiszka wrote:
> > Hi,
> >
> > while XENO_OPT_DEBUG is generally a useful switch for tracing potential
> > issues in the core and the skins, it also introduces high latencies via
> > the queue debugging feature (due to checks iterating over whole queues).
> >
> > Th
Jan Kiszka wrote:
> Hi,
>
> while XENO_OPT_DEBUG is generally a useful switch for tracing potential
> issues in the core and the skins, it also introduces high latencies via
> the queue debugging feature (due to checks iterating over whole queues).
>
> This patch introduces separate control over
18 matches
Mail list logo