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  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:   Sun, 20 Nov 2022 10:39:27 +0100
From:   Bjørn Mork <>
To:     Daniele Palmas <>
Cc:     Alexander Lobakin <>,
        David Miller <>,
        Jakub Kicinski <>,
        Paolo Abeni <>,
        Eric Dumazet <>,
        Subash Abhinov Kasiviswanathan <>,
        Sean Tranchetti <>,
        Jonathan Corbet <>,
        Greg Kroah-Hartman <>,
Subject: Re: [PATCH net-next 2/3] net: qualcomm: rmnet: add tx packets

Daniele Palmas <> writes:

> Ok, so rmnet would only take care of qmap rx packets deaggregation and
> qmi_wwan of the tx aggregation.
> At a conceptual level, implementing tx aggregation in qmi_wwan for
> passthrough mode could make sense, since the tx aggregation parameters
> belong to the physical device and are shared among the virtual rmnet
> netdevices, which can't have different aggr configurations if they
> belong to the same physical device.
> Bjørn, would this approach be ok for you?

Sounds good to me, if this can be done within the userspace API
restrictions we've been through.

I assume it's possible to make this Just Work(tm) in qmi_wwan
passthrough mode?  I do not think we want any solution where the user
will have to configure both qmi_wwan and rmnet to make things work


Powered by blists - more mailing lists