public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Frank Li <frank.li@nxp.com>, "kw@linux.com" <kw@linux.com>,
	Sherry Sun <sherry.sun@nxp.com>,
	Richard Zhu <hongxing.zhu@nxp.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: Linux PCIe EP NTB function
Date: Mon, 18 Oct 2021 09:47:39 +0530	[thread overview]
Message-ID: <459745d1-9fe7-e792-3532-33ee9552bc4d@ti.com> (raw)
In-Reply-To: <AS8PR04MB85008E09EAE36DFD6A51F4B588B89@AS8PR04MB8500.eurprd04.prod.outlook.com>

Hi Frank,

On 15/10/21 2:10 am, Frank Li wrote:
> Sorry, correct Linux-pci mail list address.
> 
>> -----Original Message-----
>> From: Frank Li
>> Sent: Thursday, October 14, 2021 3:35 PM
>> To: kishon@ti.com; kw@linux.com; Sherry Sun <sherry.sun@nxp.com>; Richard
>> Zhu <hongxing.zhu@nxp.com>
>> Cc: inux-pci@vger.kernel.org
>> Subject: Linux PCIe EP NTB function
>>
>> Kishon:
>>
>> 	We use VOP(virtio over PCIe) communication between PCI RC and EP side.
>> But VOP already removed and switch into NTB solution.
>> 	I saw you submit patch and already accepted by community about pci-
>> epf-ntb.
>>
>> 	According to document, whole system work as Device1 (PCI host) -> EP1
>> -> EP2 -> Device2(PCI host).
>> 	But our user case is Device 1(RC Host) ->  Device 2(EP).
>>
>> 	I am not sure how to apply ntb frame work into this user case.

NTB by definition is PCIe RC-to-RC communication. For RC-to-EP, see
pci_endpoint_test.c (RC) and pci-epf-test.c (EP) that provides sample endpoint
usecase.

One more RC<->EP communication model was built in [1], but that is not yet
upstreamed.

[1] -> https://lore.kernel.org/r/20200702082143.25259-1-kishon@ti.com

Thanks,
Kishon

>>
>> 	I think we can modify pci-epf-ntb to register a ntb devices. But I am
>> not sure that this is recommunicate method.  I think this user case is
>> quite common. I don't want to implement a local solution.
>>
>> 	Any suggestion?
>>
>>
>> Best regards
>> Frank Li

  reply	other threads:[~2021-10-18  4:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AS8PR04MB850055DFB524C99D64560B6188B89@AS8PR04MB8500.eurprd04.prod.outlook.com>
2021-10-14 20:40 ` Linux PCIe EP NTB function Frank Li
2021-10-18  4:17   ` Kishon Vijay Abraham I [this message]
2021-10-18 17:10     ` [EXT] " Frank Li
2021-10-21  9:59       ` Kishon Vijay Abraham I

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=459745d1-9fe7-e792-3532-33ee9552bc4d@ti.com \
    --to=kishon@ti.com \
    --cc=frank.li@nxp.com \
    --cc=hongxing.zhu@nxp.com \
    --cc=kw@linux.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=sherry.sun@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox