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:   Fri, 14 Jan 2022 21:46:32 +0100
From:   Andrew Lunn <>
To:     Alex Elder <>
Cc:     Network Development <>,
        "" <>,
        Florian Fainelli <>,
        Jakub Kicinski <>
Subject: Re: Port mirroring, v2 (RFC)

On Fri, Jan 14, 2022 at 11:03:26AM -0600, Alex Elder wrote:
> Yikes!  I don't know why that turned out double-spaced.  I hope
> this one turns out better.
> 					-Alex
> This is a second RFC for a design to implement new functionality
> in the Qualcomm IPA driver.  Since last time I've looked into some
> options based on feedback.  This time I'll provide some more detail
> about the hardware, and what the feature is doing.  And I'll end
> with two possible implementations, and some questions.
> My objective is to get a general sense that what I plan to do
> is reasonable, so the patches that implement it will be acceptable.
> The feature provides the AP access to information about the packets
> that the IPA hardware processes as it carries them between its
> "ports".  It is intended as a debug/informational interface only.
> Before going further I'll briefly explain what the IPA hardware
> does.
> The upstream driver currently uses the hardware only as the path
> that provides access to a 5G/LTE cellular network via a modem
> embedded in a Qualcomm SoC.
>        \|/
>         |
>   ------+-----   ------
>   | 5G Modem |   | AP |
>   ------------   ------
>              \\    || <-- IPA channels, or "ports"
>             -----------
>             |   IPA   |
>             -----------

Hi Alex

I think i need to take a step back here. With my background, an AP is
an 802.11 Access Point.
But here you mean Application Processor?
What does IPA standard for ?

I can probably figure these all out from context, but half the problem
here is making sure we are talking the same language when we are
considering using concepts from another part of the network stack.


Powered by blists - more mailing lists