[Lustre-discuss] InfiniBand QoS with Lustre ko2iblnd.

[Daniel Kobras]

Hi Sébastien!

On Wed, Jun 24, 2009 at 09:46:19AM +0200, Sébastien Buisson wrote:
> > - if the 'service id' information was stored on the MGS on a file system 
> > basis, one could imagine to retrieve it at mount time on the clients. 
> > The 'service id' information stored on the MGS could consist in a port 
> > space and a port id. Thus it would be possible to affect different 
> > service ports to the various connections initiated by the client, 
> > depending on the target file system.
> > What do you think? Would you say this is feasible, or can you see major 
> > issues with this proposal?
> > 
> 
> The peer's port information could be stored in the kib_peer_t structure. 
> That way, it would be possible to make clients connect to servers which 
> listen on different ports.
> What do you think?

Why do you want to distinguish the two filesystems solely by service id
rather than, say, service id + port guids of the respective Lustre
servers? You'll need a full QoS policy file instead of the simplified
syntax, and configuration needs to be adapted on hardware changes, but
this still looks simpler to me than modifying the wire protocol.

Regards,

Daniel.