From: Logan Gunthorpe <lsgunthorpe@gmail.com>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: linux-ntb <linux-ntb@googlegroups.com>
Subject: Re: Is the Scratchpad Implementation Using a LUT Standard?
Date: Wed, 11 Oct 2017 12:03:04 -0600 [thread overview]
Message-ID: <ef57a986-936e-ba87-663e-b8866a6b9fcd@gmail.com> (raw)
In-Reply-To: <20171011174114.GA25306@mobilestation>
On 11/10/17 11:41 AM, Serge Semin wrote:
> You are mistaken. IDT PCIe switch have LUT. There are 24 of them available at
> the current hardware for each NTB. All of them are available to be used over
> IDT NTB driver as well as all MWs with direct address translation.
> Additionally It is true to say about just one LUT entry usage per peer, only if
> you got just two NTB-ports available per device. What if you got eight or even more
> of them? In this case you'd need to have as many LUT entries reserved as there are
> peers available to have connections to. In this case reservation doesn't seem so
> inexpensive. As far as I can see from the switchtec brief documents, there can be
> up to 48 NTBs per device. So in this case we'd loose 48 MWs just to have some
> stupid scratchpads, which is, according to your words, a third part of all the LUT
> MWs available to a port.
Ah, fair, I wasn't aware the IDT had LUT support. Using up a third of
the LUT windows
does not seem like a problem at all considering we have no other use for
them.
Note: the switchtec code also used the shared_mw for link management,
not just
providing scratchpads. But once the upper layers are reworked to not
require
scratchpads I'd be fine with removing them from the shared_mw.
Logan
next prev parent reply other threads:[~2017-10-11 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 12:57 Is the Scratchpad Implementation Using a LUT Standard? Doug Meyer
2017-10-10 14:17 ` Allen Hubbe
2017-10-10 15:52 ` Doug Meyer
2017-10-11 16:19 ` lsgunthorpe
2017-10-11 17:41 ` Serge Semin
2017-10-11 18:03 ` Logan Gunthorpe [this message]
2017-10-12 18:31 ` D Meyer
2017-10-12 18:38 ` Logan Gunthorpe
2017-10-11 18:23 ` D Meyer
2017-10-11 18:44 ` Logan Gunthorpe
2017-10-12 18:05 ` D Meyer
2017-10-12 18:33 ` Logan Gunthorpe
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=ef57a986-936e-ba87-663e-b8866a6b9fcd@gmail.com \
--to=lsgunthorpe@gmail.com \
--cc=fancer.lancer@gmail.com \
--cc=linux-ntb@googlegroups.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