netdev - Re: cellular modem driver APIs

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] [day] [month] [year] [list]

Message-ID: <d1077ff10e664a28f0bdd38d9c178f7efd31972c.camel@sipsolutions.net>
Date:   Mon, 15 Apr 2019 10:27:57 +0200
From:   Johannes Berg <johannes@...solutions.net>
To:     Subash Abhinov Kasiviswanathan <subashab@...eaurora.org>
Cc:     Dan Williams <dcbw@...hat.com>,
        Bjørn Mork <bjorn@...k.no>,
        netdev@...r.kernel.org, Sean Tranchetti <stranche@...eaurora.org>,
        Daniele Palmas <dnlplm@...il.com>,
        Aleksander Morgado <aleksander@...ksander.es>,
        netdev-owner@...r.kernel.org
Subject: Re: cellular modem driver APIs

On Sun, 2019-04-14 at 13:09 -0600, Subash Abhinov Kasiviswanathan wrote:

> > Hmm, not sure I understand this. If you do RPS/RSS then that's a
> > hardware function, and the netdev doesn't really come into play
> > immediately? If the underlying driver directly deals with multiple
> > netdevs that's actually an *advantage*, no?
> 
> RPS is in SW only though.

I'm sort of expecting that to change in 5G, but I guess designs will
vary.

> I think this shouldn't be a concern if the existing underlying netdev 
> model could co-exist with the new framework.

Indeed. I'm just thinking that maybe a new framework shouldn't *force*
this model.

johannes