When LNet wants to send a message over a SOCKLND interface,
ksocknal_launch_packet() is called.
This calls ksocknal_launch_all_connections_locked()
This loops over all "routes" to the "peer" to make sure they all have
"connections".
If it finds a route without a connection (returned by
ksocknal_f
Adding lustre-devel alias
From: "Abe Asraoui (System)"
Date: Friday, February 14, 2020 at 3:43 PM
To: "lustre-discuss@lists.lustre.org" , "Abe
Asraoui (System)"
Subject: MDS/MDT
Hi All,
Has anyone done any meta data performance with dual ported nvmes or regular
nvmes..
Can you share what IO
Hi Cory
I'm with 2.10 there and idle disconnect is not available in 2.10.
The steps I'm thinking of so far are:
1. - Client connects, opens a TCP socket to server
2. - Client acquires a LDLM lock
3. - TCP connection gets broken
4. - Soon after a conflicting lock is enqueued. Server needs to cance
Hello, Aurélien. I'm guessing that if you have modern Lustre then idle clients
may disconnect, and so you might regularly see Lustre servers initiate the
socket connection again. I'm not sure how to show that that it is the case or
not. Perhaps someone else can chime in on whether that could
Hello,
I wanted to ask if anybody is using lustre as a FS backend for virtual
machines. I am thinking to environments like Openstack, or oVirt
where VM are inside a single qcow2 file basically using libvirt to
access the underlying filesystem where VMs are stored.
Anyone is using Lustre for this an
Thanks! That's really interesting.
Do you have a code pointer that could show where the code will establish this
connection if missing?
Le 18/02/2020 23:34, « NeilBrown » a écrit :
It is not true that:
LNET will established connections only if asked for by upper layers.