From: "Allen Hubbe" <Allen.Hubbe@emc.com>
To: 'sridhar T S' <sridhar.lochu@gmail.com>
Cc: linux-ntb@googlegroups.com
Subject: RE: Need information about understanding PCIE non-transparent bridge
Date: Fri, 6 May 2016 09:05:58 -0400 [thread overview]
Message-ID: <000001d1a798$08a195d0$19e4c170$@emc.com> (raw)
In-Reply-To: <CAO+9SsOojQ2NoRqUKCgJexBtCA=rB0JThw2q70svPAaY04-UJw@mail.gmail.com>
Hi Sridhar,
If you have NTB hardware already physically connected and
configured in your BIOS, then you can build and load the
linux ntb modules.
Here is the documentation on linux ntb modules. It says
what the modules do, and how to use them.
http://lxr.free-electrons.com/source/Documentation/ntb.txt
If you are interested in testing or demonstrating basic NTB
functionality, try ntb_tool and ntb_pingpong. There is
also a network device over NTB supported by ntb_transport
and ntb_netdev together.
Please let me know if you have any questions not answered in
the documentation. I am happy to help.
Allen
From: sridhar T S
>
> Hi allen,
>
> myself sridhar, working as senior software engineer.
> i wanted to understand about PCIE non-transparent bridge.
>
> i will be testing the linux device driver for NTB, for now
> i have a very fair understanding about the architecture.
>
> need some ideas about how to test the NTB device driver
> across NTB systems for proper system operations with
> respect to NTB device driver for linux
>
> your inputs and information will be helpful.
>
> thanks in advance.
>
> regards,
> Sridhar
next parent reply other threads:[~2016-05-06 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAO+9SsOojQ2NoRqUKCgJexBtCA=rB0JThw2q70svPAaY04-UJw@mail.gmail.com>
2016-05-06 13:05 ` Allen Hubbe [this message]
2016-05-09 9:23 ` Need information about understanding PCIE non-transparent bridge sridhar T S
2016-05-09 12:11 ` Jon Mason
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='000001d1a798$08a195d0$19e4c170$@emc.com' \
--to=allen.hubbe@emc.com \
--cc=linux-ntb@googlegroups.com \
--cc=sridhar.lochu@gmail.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