[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9175f51f-2db4-84fd-01ba-0047ce8ebdcc@linaro.org>
Date: Tue, 18 Jan 2022 12:14:22 -0600
From: Alex Elder <elder@...aro.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Andrew Lunn <andrew@...n.ch>,
Network Development <netdev@...r.kernel.org>,
"bjorn.andersson@...aro.org" <bjorn.andersson@...aro.org>,
Florian Fainelli <f.fainelli@...il.com>
Subject: Re: Port mirroring, v2 (RFC)
On 1/18/22 12:07 PM, Jakub Kicinski wrote:
> On Fri, 14 Jan 2022 15:12:41 -0600 Alex Elder wrote:
>>> I think i need to take a step back here. With my background, an AP is
>>> an 802.11 Access Point.
>>
>> Again, terminology problems! Sorry about that.
>>
>> Yes, when I say "AP" I mean "Application Processor". Some people
>> might call it "APSS" for "Application Processor Subsystem."
>
> And AP is where Linux runs, correct? Because there are also APs on NICs
> (see ETH_RESET_AP) which are not the host...
Correct. It is the term I have used consistently in the
IPA code, to refer to "the processor (complex) running
Linux, which (basically) owns the IPA device."
-Alex
Powered by blists - more mailing lists