From: Bjorn Helgaas <helgaas@kernel.org>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: linux-kernel@vger.kernel.org, linux-ntb@googlegroups.com,
linux-pci@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-kselftest@vger.kernel.org, Jon Mason <jdmason@kudzu.us>,
Joerg Roedel <joro@8bytes.org>, Allen Hubbe <allenbh@gmail.com>,
Dave Jiang <dave.jiang@intel.com>,
Serge Semin <fancer.lancer@gmail.com>,
Eric Pilmore <epilmore@gigaio.com>
Subject: Re: [PATCH v3 03/10] NTB: Introduce helper functions to calculate logical port number
Date: Fri, 22 Mar 2019 11:51:12 -0500 [thread overview]
Message-ID: <20190322165111.GO251185@google.com> (raw)
In-Reply-To: <20190322000645.15580-4-logang@deltatee.com>
On Thu, Mar 21, 2019 at 06:06:38PM -0600, Logan Gunthorpe wrote:
> This patch introduces the "Logical Port Number" which is similar to the
> "Port Number" in that it enumerates the ports in the system.
>
> The original (or Physical) "Port Number" can be any number used by the
> hardware to uniquley identify a port in the system. The "Logical Port
s/uniquley/uniquely/
> Number" enumerates all ports in the system from 0 to the number of
> ports minus one.
>
> For example a system with 5 ports might have the following port numbers
> which would be enumareted thusly:
s/enumareted/enumerated/
> + * ntb_logical_port_number() - get the logical port number of the local port
> + * @ntb: NTB device context.
> + *
> + * The Logical Port Number is defined to be a unique number for each
> + * port starting from zero through to the number of ports minus one.
> + * This is in contrast to the Port Number where each port can be assigned
> + * any unqique physical number by the hardware.
s/unqique/unique/
> + * ntb_peer_logical_port_number() - get the logical peer port by given index
> + * @ntb: NTB device context.
> + * @pidx: Peer port index.
> + *
> + * The Logical Port Number is defined to be a unique number for each
> + * port starting from zero through to the number of ports minus one.
> + * This is in contrast to the Port Number where each port can be assigned
> + * any unqique physical number by the hardware.
s/unqique/unique/
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: helgaas at kernel.org (Bjorn Helgaas)
Subject: [PATCH v3 03/10] NTB: Introduce helper functions to calculate logical port number
Date: Fri, 22 Mar 2019 11:51:12 -0500 [thread overview]
Message-ID: <20190322165111.GO251185@google.com> (raw)
In-Reply-To: <20190322000645.15580-4-logang@deltatee.com>
On Thu, Mar 21, 2019 at 06:06:38PM -0600, Logan Gunthorpe wrote:
> This patch introduces the "Logical Port Number" which is similar to the
> "Port Number" in that it enumerates the ports in the system.
>
> The original (or Physical) "Port Number" can be any number used by the
> hardware to uniquley identify a port in the system. The "Logical Port
s/uniquley/uniquely/
> Number" enumerates all ports in the system from 0 to the number of
> ports minus one.
>
> For example a system with 5 ports might have the following port numbers
> which would be enumareted thusly:
s/enumareted/enumerated/
> + * ntb_logical_port_number() - get the logical port number of the local port
> + * @ntb: NTB device context.
> + *
> + * The Logical Port Number is defined to be a unique number for each
> + * port starting from zero through to the number of ports minus one.
> + * This is in contrast to the Port Number where each port can be assigned
> + * any unqique physical number by the hardware.
s/unqique/unique/
> + * ntb_peer_logical_port_number() - get the logical peer port by given index
> + * @ntb: NTB device context.
> + * @pidx: Peer port index.
> + *
> + * The Logical Port Number is defined to be a unique number for each
> + * port starting from zero through to the number of ports minus one.
> + * This is in contrast to the Port Number where each port can be assigned
> + * any unqique physical number by the hardware.
s/unqique/unique/
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: helgaas@kernel.org (Bjorn Helgaas)
Subject: [PATCH v3 03/10] NTB: Introduce helper functions to calculate logical port number
Date: Fri, 22 Mar 2019 11:51:12 -0500 [thread overview]
Message-ID: <20190322165111.GO251185@google.com> (raw)
Message-ID: <20190322165112.DulXSLi4gRt5qyvJvQPHnwFhIlk3mPVcfYZxXRFRu6Q@z> (raw)
In-Reply-To: <20190322000645.15580-4-logang@deltatee.com>
On Thu, Mar 21, 2019@06:06:38PM -0600, Logan Gunthorpe wrote:
> This patch introduces the "Logical Port Number" which is similar to the
> "Port Number" in that it enumerates the ports in the system.
>
> The original (or Physical) "Port Number" can be any number used by the
> hardware to uniquley identify a port in the system. The "Logical Port
s/uniquley/uniquely/
> Number" enumerates all ports in the system from 0 to the number of
> ports minus one.
>
> For example a system with 5 ports might have the following port numbers
> which would be enumareted thusly:
s/enumareted/enumerated/
> + * ntb_logical_port_number() - get the logical port number of the local port
> + * @ntb: NTB device context.
> + *
> + * The Logical Port Number is defined to be a unique number for each
> + * port starting from zero through to the number of ports minus one.
> + * This is in contrast to the Port Number where each port can be assigned
> + * any unqique physical number by the hardware.
s/unqique/unique/
> + * ntb_peer_logical_port_number() - get the logical peer port by given index
> + * @ntb: NTB device context.
> + * @pidx: Peer port index.
> + *
> + * The Logical Port Number is defined to be a unique number for each
> + * port starting from zero through to the number of ports minus one.
> + * This is in contrast to the Port Number where each port can be assigned
> + * any unqique physical number by the hardware.
s/unqique/unique/
Bjorn
next prev parent reply other threads:[~2019-03-22 16:51 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 0:06 [PATCH v3 00/10] Support using MSI interrupts in ntb_transport Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` logang
2019-03-22 0:06 ` [PATCH v3 01/10] PCI/MSI: Support allocating virtual MSI interrupts Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` logang
2019-03-22 0:06 ` [PATCH v3 02/10] PCI/switchtec: Add module parameter to request more interrupts Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` logang
2019-03-22 0:06 ` [PATCH v3 03/10] NTB: Introduce helper functions to calculate logical port number Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` logang
2019-03-22 16:51 ` Bjorn Helgaas [this message]
2019-03-22 16:51 ` Bjorn Helgaas
2019-03-22 16:51 ` helgaas
2019-03-22 0:06 ` [PATCH v3 04/10] NTB: Introduce functions to calculate multi-port resource index Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` logang
2019-03-22 0:06 ` [PATCH v3 05/10] NTB: Rename ntb.c to support multiple source files in the module Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` logang
2019-03-22 0:06 ` [PATCH v3 06/10] NTB: Introduce MSI library Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` logang
2019-03-22 0:06 ` [PATCH v3 07/10] NTB: Introduce NTB MSI Test Client Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` logang
2019-03-22 0:06 ` [PATCH v3 08/10] NTB: Add ntb_msi_test support to ntb_test Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` logang
2019-03-22 0:06 ` [PATCH v3 09/10] NTB: Add MSI interrupt support to ntb_transport Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` logang
2019-03-22 16:47 ` Bjorn Helgaas
2019-03-22 16:47 ` Bjorn Helgaas
2019-03-22 16:47 ` helgaas
2019-03-25 19:08 ` Logan Gunthorpe
2019-03-25 19:08 ` Logan Gunthorpe
2019-03-25 19:08 ` Logan Gunthorpe
2019-03-25 19:08 ` logang
2019-03-22 0:06 ` [PATCH v3 10/10] NTB: Describe the ntb_msi_test client in the documentation Logan Gunthorpe
2019-03-22 0:06 ` Logan Gunthorpe
2019-03-22 0:06 ` logang
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=20190322165111.GO251185@google.com \
--to=helgaas@kernel.org \
--cc=allenbh@gmail.com \
--cc=dave.jiang@intel.com \
--cc=epilmore@gigaio.com \
--cc=fancer.lancer@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jdmason@kudzu.us \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.