From: Jakub Kicinski <kuba@kernel•org>
To: Alexander Duyck <alexander.duyck@gmail•com>
Cc: Edward Cree <ecree.xilinx@gmail•com>,
ecree@xilinx•com, netdev@vger•kernel.org, davem@davemloft•net,
pabeni@redhat•com, edumazet@google•com, corbet@lwn•net,
linux-doc@vger•kernel.org, linux-net-drivers@amd•com,
Jacob Keller <jacob.e.keller@intel•com>,
Jesse Brandeburg <jesse.brandeburg@intel•com>,
Michael Chan <michael.chan@broadcom•com>,
Andy Gospodarek <andy@greyhouse•net>,
Saeed Mahameed <saeed@kernel•org>, Jiri Pirko <jiri@resnulli•us>,
Shannon Nelson <snelson@pensando•io>,
Simon Horman <simon.horman@corigine•com>
Subject: Re: [RFC PATCH net-next] docs: net: add an explanation of VF (and other) Representors
Date: Thu, 11 Aug 2022 09:17:20 -0700 [thread overview]
Message-ID: <20220811091720.1e82eb46@kernel.org> (raw)
In-Reply-To: <CAKgT0UdLFjxdxHTPb7c+Deih2Bciziz=gZxDYWUFsLNNetOFQg@mail.gmail.com>
On Wed, 10 Aug 2022 15:58:54 -0700 Alexander Duyck wrote:
> > Sure, but as an application of that, people talk about e.g. "host"
> > and "device" ends of a bus, DMA transfer, etc. As a result of which
> > "host" has come to mean "computer; server; the big rack-mounted box
> > you plug cards into".
> > A connotation which is unfortunate once a single device can live on
> > two separate PCIe hierarchies, connected to two computers each with
> > its own hostname, and the one which owns the device is the cluster
> > of embedded CPUs inside the card, rather than the big metal box.
>
> I agree that "host" isn't going to work as a multi-host capable device
> might end up having only one "host" that can actually handle the
> configuration of the switch for the entire device. So then you have
> different types of "host" interfaces.
Thank $deity I haven't had to think about multi-host NPU/DPU/IPUs
for a couple of years now, but I think trying to elect a leader in
charge across the hosts is not a good idea there. Much easier to proxy
all configuration thru FW, as much as I hate that (since FW is usually
closed).
That said choosing the term is about intuition not proofs so "host"
won't fly.
prev parent reply other threads:[~2022-08-11 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 16:58 [RFC PATCH net-next] docs: net: add an explanation of VF (and other) Representors ecree
2022-08-05 19:15 ` Randy Dunlap
2022-08-08 20:48 ` Edward Cree
2022-08-06 1:43 ` Jakub Kicinski
2022-08-08 16:50 ` Keller, Jacob E
2022-08-08 20:44 ` Edward Cree
2022-08-09 3:41 ` Jakub Kicinski
2022-08-10 16:02 ` Edward Cree
2022-08-10 17:58 ` Jakub Kicinski
2022-08-10 19:21 ` Edward Cree
2022-08-10 22:58 ` Alexander Duyck
2022-08-11 16:17 ` Jakub Kicinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220811091720.1e82eb46@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=alexander.duyck@gmail$(echo .)com \
--cc=andy@greyhouse$(echo .)net \
--cc=corbet@lwn$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=ecree.xilinx@gmail$(echo .)com \
--cc=ecree@xilinx$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=jacob.e.keller@intel$(echo .)com \
--cc=jesse.brandeburg@intel$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-net-drivers@amd$(echo .)com \
--cc=michael.chan@broadcom$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=saeed@kernel$(echo .)org \
--cc=simon.horman@corigine$(echo .)com \
--cc=snelson@pensando$(echo .)io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox