All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nic Henke <nic@cray.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] extend lnet_notify to public LNet API
Date: Wed, 17 Nov 2010 08:59:43 -0600	[thread overview]
Message-ID: <4CE3EDDF.2090007@cray.com> (raw)
In-Reply-To: <9EC72A67-A9FB-41A8-8564-99903E08F047@clusterstor.com>

On 11/17/2010 01:52 AM, Alexey Lyashkov wrote:
> Nic,
>
> that idea discussed some time ago (as i remember with green and maxim), but have some objection.
> Currently LNet hide from ptlrpc layer any network flaps, and LNet will resend request without notify ptlrpc about flap until ptlrpc request timeout.

I'm missing something - to my knowledge, LNet never retries messages.

> But if ptlrpc will see node down event, ptlrpc will try reconnect  - that will produce extra overhead, because need to resend too much requests from sending and delay lists instead of lots requests in network flap time.
> So, you need separate network flap from node down situation - before implementing that.
> currently node marked down if node don't respond for request in ptlrpc timeout, which include network transmit and processing times, but it different then LNet message timeout.

I think that is a valid upper layer decision to make, but separate from 
implementing the LNet callbacks on network 'flap'. I wouldn't want to 
force ptlrpc to use it.

Cheers,
Nic

  reply	other threads:[~2010-11-17 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 16:00 [Lustre-devel] extend lnet_notify to public LNet API Nic Henke
2010-11-17  3:00 ` liang Zhen
2010-11-17  7:52 ` Alexey Lyashkov
2010-11-17 14:59   ` Nic Henke [this message]
2010-11-22 17:23     ` Nic Henke
2010-11-22 17:29 ` Nic Henke
2010-11-24 13:10   ` Eric Barton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CE3EDDF.2090007@cray.com \
    --to=nic@cray.com \
    --cc=lustre-devel@lists.lustre.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.