On Wed, Jun 7, 2017 at 5:02 PM, Alexandru Ardelean
wrote:
> On Wed, Jun 7, 2017 at 4:48 PM, Felix Fietkau wrote:
>> On 2017-06-07 15:44, Felix Fietkau wrote:
>>> On 2017-06-07 13:09, Alexandru Ardelean wrote:
It's not very often that the tx_queue is used,
to store backlog messages to se
On Wed, Jun 7, 2017 at 4:48 PM, Felix Fietkau wrote:
> On 2017-06-07 15:44, Felix Fietkau wrote:
>> On 2017-06-07 13:09, Alexandru Ardelean wrote:
>>> It's not very often that the tx_queue is used,
>>> to store backlog messages to send to a client.
>>>
>>> And for most cases, 32 backlog messages s
On 2017-06-07 15:44, Felix Fietkau wrote:
> On 2017-06-07 13:09, Alexandru Ardelean wrote:
>> It's not very often that the tx_queue is used,
>> to store backlog messages to send to a client.
>>
>> And for most cases, 32 backlog messages seems to be enough.
>> In fact, for most cases, I've seen ~1
On 2017-06-07 13:09, Alexandru Ardelean wrote:
> It's not very often that the tx_queue is used,
> to store backlog messages to send to a client.
>
> And for most cases, 32 backlog messages seems to be enough.
> In fact, for most cases, I've seen ~1 entry in the queue
> being used every now-n-then.
On Wed, Jun 7, 2017 at 2:09 PM, Alexandru Ardelean
wrote:
> It's not very often that the tx_queue is used,
> to store backlog messages to send to a client.
>
> And for most cases, 32 backlog messages seems to be enough.
> In fact, for most cases, I've seen ~1 entry in the queue
> being used every
It's not very often that the tx_queue is used,
to store backlog messages to send to a client.
And for most cases, 32 backlog messages seems to be enough.
In fact, for most cases, I've seen ~1 entry in the queue
being used every now-n-then.
The issue is more visible/present with the `ubus list` co
