nlmills / xdd Goto Github PK
View Code? Open in Web Editor NEWThis project forked from bws/xdd
XDD - The eXtreme dd toolset
License: GNU General Public License v2.0
This project forked from bws/xdd
XDD - The eXtreme dd toolset
License: GNU General Public License v2.0
Build Instructions for XDD release -- Supported OS: Linux, AIX, OSX On supported OS: > ./configure > make > make install By default, XDD and supporting scripts are installed in /usr/bin and /usr/lib, in order to change the installation path, use --prefix=<new path> during the configure step. By default, the following features are enabled: XFS support, NUMA support, and Infiniband support. If you do not need these features, or cannot install the relevant support libraries, you can disable each of these features individually during configure with the following flags, respectively: --disable-xfs, --disable-numa, and --disable-ib. Build instructions for XDD repository code -- If you are using the git repository version of XDD (i.e. you are a prospective XDD developer), you will need to add one more step during the software build process. We also suggest enabling debug mode. On supported OS: > autoconf > ./configure --enable-debug > make > make install XFS pre-allocation support -- File preallocation on end-to-end transfers currently only works for the XFS file system. This is mainly because the posix_fallocate call is supported inconsistently in Linux, and so we are making the direct fctl call in the case of XFS file systems. We attempt to enable preallocate on XFS if we can find the correct headers in the default places. But if the headers are not easily locatable then we do not enable XFS preallocation support. The configure script controls xfs preallocation with with an explicit enable/disable flag. To guarantee that XFS preallocation is enable, use the following: > ./configure --enable-xfs To disable XFS preallocation, use the following instead: > ./configure --disable-xfs The defaults have been tested on Fedora 12, Scientific Linux, and Suse only. Qdepth/Thread count advisory -- In XDD, the number of threads is often governed by the queue depth option or the thread count option. The number of threads than may be created is system dependent. For example, on my laptop I can only create 916 threads before the system returns a "resource busy or unavailable" error. Its not just a simple memory limitation necessarily either (i.e. reducing the pthread stack size doesn't automatically increase the number of threads you can create). In general, the number of threads that can be initialized by XDD is limited by the system rather than XDD. This is mainly interesting when using fork-thread type access patterns.
Currently the xddmcp script opens an ssh session using the current user's name. However, it is desirable to allow the user to connect using a username specified on the command line.
The old e2e code sent a special EOF packet, but XNI expects you to close the connection. Will XNI be able to close and open the connection again for every pass? If not, the protocol may have to be expanded or multiple passes disabled for remote transfers.
This feature was removed with commit 3aae5d1.
When xddmcp prompts for a password it always uses the current username, even when a different username is given in the path spec. It should use the username given in the path spec. If no username was given then it can default to the current user.
Make XNI TCP the default for end-to-end transfers so that it isn't required to specify the -xni tcp
option each time. Currently, if you attempt to transfer end-to-end without any -xni
option you get the error
xdd: xint_e2e_target_init: could not initialize XNI for e2e target
Without this feature the transfer scripts like xddmcp are broken (they were built to use the older e2e code that has been removed).
Currently the TCP window size is always the value of DEFAULT_E2E_TCP_WINDOW_SIZE
= 16 MiB. For long distances an even larger window size may be desirable.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.