[lustre-devel] Why can you set concurrent_sends < peer_credits ?

Alexey Lyashkov alexey.lyashkov at seagate.com
Wed Aug 19 13:54:57 PDT 2015

In my invested case, I have see large number tx in sending queue with
negative credits. it's mean we don't able to resend these messages via
different gateway until message expired. But if we stop to queue messages
with reach a zero credits, we will able to send message via different
gateway after peer dead event without any notifications to ptlrpc layer. So
i think it's likely to be a bug as from my point view, we need to avoid
ptlrpc reconnects as possible.

On Wed, Aug 19, 2015 at 11:48 PM, Christopher J. Morrone <morrone2 at llnl.gov>

> LNet does stop sending LNet messages on a peer connection when that peer's
> credit count reaches zero.  LNet chose to then relate the count of messages
> awaiting credits by using negative values of the same variable.  It is just
> the convention chosen, and doesn't necessarily mean that there is a design
> problem there.

Alexey Lyashkov *·* Technical lead for a Morpheus team
Seagate Technology, LLC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20150819/ab345067/attachment.htm>

More information about the lustre-devel mailing list