Warning: main(/www/www/htdocs/style/globals.php) [function.main]: failed to open stream: No such file or directory in /www/www/docs/6.4.1/io-pkt_en/user_guide/tdp.html on line 1
Warning: main() [function.include]: Failed opening '/www/www/htdocs/style/globals.php' for inclusion (include_path='.:/www/www/common:/www/www/php/lib/php') in /www/www/docs/6.4.1/io-pkt_en/user_guide/tdp.html on line 1
Warning: main(/www/www/htdocs/style/header.php) [function.main]: failed to open stream: No such file or directory in /www/www/docs/6.4.1/io-pkt_en/user_guide/tdp.html on line 8
Warning: main() [function.include]: Failed opening '/www/www/htdocs/style/header.php' for inclusion (include_path='.:/www/www/common:/www/www/php/lib/php') in /www/www/docs/6.4.1/io-pkt_en/user_guide/tdp.html on line 8
This chapter includes:
Transparent Distributed Processing (also known as Qnet) functions the same
under the old io-net and new io-pkt infrastructures,
and the packet format and protocol remain the same.
For both io-net and io-pkt, Qnet is just another
protocol (like TCP/IP) that transmits and receives packets.
The Qnet module in Core Networking is now a loadable shared module,
lsm-qnet.so.
We support only the l4_lw_lite variant;
we no longer support the qnet-compat variant that was
compatible with Neutrino 6.2.1.
To start the stack with Qnet, type this command:
io-pkt-v4 -ddriver -pqnet
(assuming you have your PATH and LD_LIBRARY_PATH
environment variables set up properly).
You can also mount the protocol after the stack has started, like this:
mount -Tio-pkt full_path_to_dll/lsm-qnet.so
Note that mount still supports the io-net option,
to provide backward compatibility with existing scripts.
The command-line options and general configuration information are the same
as they were with io-net.
For more information, see
lsm-qnet.so
in the Utilities Reference.
TDP supports two modes of communications: one directly over Ethernet,
and one over IP.
The “straight to Ethernet” L4 layer is faster and more dynamic
than the IP layer, but it isn't possible to route
TDP packets out of a single layer-2 domain.
By using TDP over IP, you can connect to any remote machine over the Internet
as follows:
- TDP must use the DNS resolver to get an IP address from a hostname
(i.e. use the resolve=dns option).
Configure the local host name and domain, and then make sure that
gethostbyname()
can resolve all the host names that you want to talk to (including the
local machine):
- Use
hostname
to set the host name.
- Use
setconf
to set the _CS_DOMAIN configuration string to indicate
your domain.
- If the hosts aren't in a DNS database, create an appropriate name to host
resolution file in /etc/hosts which includes the fully qualified node name
(including domain) and change the resolver to use the host file instead of
using the DNS server.
(e.g. setconf _CS_RESOLVE lookup_file_bind)
For more information on name resolution, see the "Name servers" section in
TCP/IP Networking.
- Start (or mount) Qnet with the bind=ip,resolve=dns options.
For example:
io-pkt-v4-hc -di82544 -pqnet bind=ip,resolve=dns
or:
mount -Tio-pkt -o bind-ip,resolve=dns full_path_to_dll/lsm-qnet.so
With raw Ethernet transport, names automatically appear in the
/net directory.
This doesn't happen with TDP over IP;
as you perform TDP operations (e.g. ls /net/host1),
the entries are created as required.
Warning: main(/www/www/htdocs/style/footer.php) [function.main]: failed to open stream: No such file or directory in /www/www/docs/6.4.1/io-pkt_en/user_guide/tdp.html on line 172
Warning: main() [function.include]: Failed opening '/www/www/htdocs/style/footer.php' for inclusion (include_path='.:/www/www/common:/www/www/php/lib/php') in /www/www/docs/6.4.1/io-pkt_en/user_guide/tdp.html on line 172