From: Zhi Li <lznuaa@gmail.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
kishon@ti.com, lorenzo.pieralisi@arm.com, kw@linux.com,
Jingoo Han <jingoohan1@gmail.com>,
gustavo.pimentel@synopsys.com, hongxing.zhu@nxp.com,
Jon Mason <jdmason@kudzu.us>, Dave Jiang <dave.jiang@intel.com>,
Allen Hubbe <allenbh@gmail.com>,
linux-ntb@googlegroups.com, linux-pci@vger.kernel.org,
ntb@lists.linux.dev
Subject: Re: [PATCH V2 0/4] NTB function for PCIe RC to EP connection
Date: Mon, 4 Apr 2022 15:12:17 -0500 [thread overview]
Message-ID: <CAHrpEqRBEp=201oc4qv7YT68u+KH5EaaG=Ln_Y5ypmKagWM6Qg@mail.gmail.com> (raw)
In-Reply-To: <CAHrpEqTTuJhK5-kB7Q2SLt3uTvcef+ehDUA8v_f1-Zna1UN+CQ@mail.gmail.com>
On Thu, Mar 10, 2022 at 4:07 PM Zhi Li <lznuaa@gmail.com> wrote:
>
> On Thu, Mar 10, 2022 at 4:01 PM Zhi Li <lznuaa@gmail.com> wrote:
> >
> > On Tue, Feb 22, 2022 at 10:24 AM Frank Li <Frank.Li@nxp.com> wrote:
> > >
> > > This implement NTB function for PCIe EP to RC connections.
> > > The existed ntb epf need two PCI EPs and two PCI Host.
> > >
> > > This just need EP to RC connections.
> > >
> > > ┌────────────┐ ┌─────────────────────────────────────┐
> > > │ │ │ │
> > > ├────────────┤ │ ┌──────────────┤
> > > │ NTB │ │ │ NTB │
> > > │ NetDev │ │ │ NetDev │
> > > ├────────────┤ │ ├──────────────┤
> > > │ NTB │ │ │ NTB │
> > > │ Transfer │ │ │ Transfer │
> > > ├────────────┤ │ ├──────────────┤
> > > │ │ │ │ │
> > > │ PCI NTB │ │ │ │
> > > │ EPF │ │ │ │
> > > │ Driver │ │ │ PCI Virtual │
> > > │ │ ├───────────────┐ │ NTB Driver │
> > > │ │ │ PCI EP NTB │◄────►│ │
> > > │ │ │ FN Driver │ │ │
> > > ├────────────┤ ├───────────────┤ ├──────────────┤
> > > │ │ │ │ │ │
> > > │ PCI BUS │ ◄─────► │ PCI EP BUS │ │ Virtual PCI │
> > > │ │ PCI │ │ │ BUS │
> > > └────────────┘ └───────────────┴──────┴──────────────┘
> > > PCI RC PCI EP
> > >
> > >
> > >
> > > Frank Li (4):
> > > PCI: designware-ep: Allow pci_epc_set_bar() update inbound map address
> > > NTB: epf: Allow more flexibility in the memory BAR map method
> > > PCI: endpoint: Support NTB transfer between RC and EP
> > > Documentation: PCI: Add specification for the PCI vNTB function device
> > >
> >
>
> Update ntb mail list
Friendly ping!
Frank Li
>
> >
> > > Documentation/PCI/endpoint/index.rst | 2 +
> > > .../PCI/endpoint/pci-vntb-function.rst | 126 ++
> > > Documentation/PCI/endpoint/pci-vntb-howto.rst | 167 ++
> > > drivers/ntb/hw/epf/ntb_hw_epf.c | 48 +-
> > > .../pci/controller/dwc/pcie-designware-ep.c | 10 +-
> > > drivers/pci/endpoint/functions/Kconfig | 11 +
> > > drivers/pci/endpoint/functions/Makefile | 1 +
> > > drivers/pci/endpoint/functions/pci-epf-vntb.c | 1424 +++++++++++++++++
> > > 8 files changed, 1775 insertions(+), 14 deletions(-)
> > > create mode 100644 Documentation/PCI/endpoint/pci-vntb-function.rst
> > > create mode 100644 Documentation/PCI/endpoint/pci-vntb-howto.rst
> > > create mode 100644 drivers/pci/endpoint/functions/pci-epf-vntb.c
> > >
> > > --
> > > 2.24.0.rc1
> > >
next prev parent reply other threads:[~2022-04-04 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220222162355.32369-1-Frank.Li@nxp.com>
[not found] ` <CAHrpEqTFP7SUgoTFq5Dn2-rOrAL_DCX97nRww7o_xnDJ+zDmtw@mail.gmail.com>
2022-03-10 22:07 ` [PATCH V2 0/4] NTB function for PCIe RC to EP connection Zhi Li
2022-04-04 20:12 ` Zhi Li [this message]
[not found] ` <20220222162355.32369-3-Frank.Li@nxp.com>
2022-03-10 22:08 ` [PATCH v2 2/4] NTB: epf: Allow more flexibility in the memory BAR map method Zhi Li
[not found] ` <20220222162355.32369-4-Frank.Li@nxp.com>
2022-03-10 22:09 ` [PATCH v2 3/4] PCI: endpoint: Support NTB transfer between RC and EP Zhi Li
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='CAHrpEqRBEp=201oc4qv7YT68u+KH5EaaG=Ln_Y5ypmKagWM6Qg@mail.gmail.com' \
--to=lznuaa@gmail.com \
--cc=Frank.Li@nxp.com \
--cc=allenbh@gmail.com \
--cc=dave.jiang@intel.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=helgaas@kernel.org \
--cc=hongxing.zhu@nxp.com \
--cc=jdmason@kudzu.us \
--cc=jingoohan1@gmail.com \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=linux-ntb@googlegroups.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=ntb@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).