Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] SPDK failed to access CMB cards
Date: Tue, 19 Jun 2018 16:20:45 +0000	[thread overview]
Message-ID: <2f696cf3fd90e5453dbda2c161da8c0e6ec35f49.camel@intel.com> (raw)
In-Reply-To: CABe79T6oU+2964Q-hC9x5AuVdT4oM1aNdEqvghLVjOCv5qZwOg@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]

On Mon, 2018-06-18 at 20:33 +0530, Srinath Mannam wrote:
> Outbound mapping in our platforms, CPU address is not same as PCI bus address.
> If we program CPU address (CMB bar physical address) as SQ address. then CMB
> card will send read request  to corresponding CPU address over PCIe bus, which
> is invalid inbound address to our RC so it is rejected as UR.
> 
> For the same issue, we have a fix in kernel driver. The fix is, SQ address has
> to configure rather PCI bus address than CPU address.
> In this case CMB card read SQ from its local memory (CMB bar memory) without
> generating memory read on PCIe bus.
> 
> We need same type of fix in spdk nvme library also.
> 
> We think two different solutions to solve this issue.
> 1. Get PCI bus address to corresponding CPU address (SMB bar address) through
> sysfs entry, in the same way we get BAR phy address with the read of
> "resource" file in sysfs. This case we program PCI bus address as SQ address. 
> This fix is similar to the kernel driver fix. 

Which sysfs entry contains the proper address?

Thanks,
Ben

             reply	other threads:[~2018-06-19 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19 16:20 Walker, Benjamin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-26 10:02 [SPDK] SPDK failed to access CMB cards Srinath Mannam
2018-06-18 15:03 Srinath Mannam

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=2f696cf3fd90e5453dbda2c161da8c0e6ec35f49.camel@intel.com \
    --to=spdk@lists.01.org \
    /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