netdev - Re: RMNET QMAP data aggregation with size greater than 16384

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 13 Aug 2021 08:25:14 +0200
From:   Bjørn Mork <bjorn@...k.no>
To:     subashab@...eaurora.org
Cc:     Daniele Palmas <dnlplm@...il.com>,
        Aleksander Morgado <aleksander@...ksander.es>,
        Network Development <netdev@...r.kernel.org>,
        Sean Tranchetti <stranche@...eaurora.org>
Subject: Re: RMNET QMAP data aggregation with size greater than 16384

subashab@...eaurora.org writes:

>> Just an heads-up that when I proposed that urb size there were doubts
>> about the value (see
>> https://patchwork.ozlabs.org/project/netdev/patch/20200909091302.20992-1-dnlplm@gmail.com/#2523774
>> and
>> https://patchwork.ozlabs.org/project/netdev/patch/20200909091302.20992-1-dnlplm@gmail.com/#2523958):
>> it is true that this time you are setting the size just when qmap is
>> enabled, but I think that Carl's comment about low-cat chipsets could
>> still apply.
>> Thanks,
>> Daniele
>> 
>
> Thanks for bringing this up.
>
> Looks like a tunable would be needed to satisfy all users.
> Perhaps we can use 32k as default in mux and passthrough mode but
> allow for changes
> there if needed through a sysfs.

Sounds reasonable to me.



Bjørn