23.07.2014 Views

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

31.2.4 RapidArray LND<br />

The RapidArray LND (ralnd) is connection-based and uses the acceptor to establish<br />

connections with its peers. It is limited to a single instance, which uses all (both)<br />

RapidArray devices present. It load balances over them using the XOR of the source<br />

and destination NIDs to determine which device to use for communication.<br />

The address-within-network is determined by the address of the single IP interface<br />

that may be specified by the "networks" module parameter. If this is omitted, then<br />

the first non-loopback IP interface that is up is used instead.<br />

Variable<br />

n_connd<br />

(4)<br />

min_reconnect_interv<br />

al<br />

(1,W)<br />

max_reconnect_interv<br />

al<br />

(60,W)<br />

timeout<br />

(30,W)<br />

ntx<br />

(64)<br />

ntx_nblk<br />

(256)<br />

fma_cq_size<br />

(8192)<br />

max_immediate<br />

(2048,W)<br />

Description<br />

Sets the number of connection daemons.<br />

Minimum connection retry interval (in seconds). After a failed<br />

connection attempt, this sets the time that must elapse before the<br />

first retry. As connections attempts fail, this time is doubled on<br />

each successive retry, up to a maximum of the<br />

max_reconnect_interval option.<br />

Maximum connection retry interval (in seconds).<br />

Time (in seconds) that communications may be stalled before the<br />

LND completes them with failure.<br />

Number of "normal" message descriptors for locally-initiated<br />

communications that may block for memory (callers block when<br />

this pool is exhausted).<br />

Number of "reserved" message descriptors for communications<br />

that may not block for memory. This pool must be sized large<br />

enough so it is never exhausted.<br />

Number of entries in the RapidArray FMA completion queue to<br />

allocate. It should be increased if the ralnd starts to issue warnings<br />

that the FMA CQ has overflowed. This is only a performance issue.<br />

Size (in bytes) of the smallest message that will be RDMA’d, rather<br />

than being included as immediate data in an FMA. All messages<br />

greater than 6912 bytes must be RDMA’d (FMA limit).<br />

Chapter 31 Configuration Files and Module Parameters (man5) 31-11

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!