From: Ben Evans <bevans@cray.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] adding IOCTL for ping
Date: Mon, 21 Sep 2015 14:31:30 +0000 [thread overview]
Message-ID: <D2258CC0.183A%jevans@cray.com> (raw)
In-Reply-To: <F29A015B-AF57-4564-8B69-A8DC05292784@intel.com>
Nope, looks like I was missing something, I wasn?t terribly familiar with
pingless clients and the external health networks. Reading up on those
now.
-Ben
On 9/21/15, 5:41 AM, "Dilger, Andreas" <andreas.dilger@intel.com> wrote:
>Maybe I'm missing something here, but why not disable pinging altogether
>at this point and depend on the external health network? That is already
>possible today via https://jira.hpdd.intel.com/browse/LU-2467.
>
>Cheers, Andreas
>
>On Sep 15, 2015, at 17:05, Ben Evans
><bevans at cray.com<mailto:bevans@cray.com>> wrote:
>
>Would there be any interest in adding an IOCTL to update the ping
>time/status for a particular NID?
>
>This should allow for implementation of a pinger in userspace which
>updates the kernel on the status of various NIDs, and if I understand the
>ping code well enough, would greatly curtail any pings that is sent by
>the kernel.
>
>This might allow for things like Eric?s gossip implementation to simply
>bolt on top of Lustre without any internal kernel changes, or for
>integration of external monitoring systems to tell Lustre that failovers
>have occurred, etc.
>
>-Ben Evans
>_______________________________________________
>lustre-devel mailing list
>lustre-devel at lists.lustre.org<mailto:lustre-devel@lists.lustre.org>
>http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
prev parent reply other threads:[~2015-09-21 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 15:04 [lustre-devel] adding IOCTL for ping Ben Evans
2015-09-15 20:37 ` Christopher J. Morrone
2015-09-15 20:53 ` Ben Evans
2015-09-15 21:12 ` Patrick Farrell
2015-09-16 13:10 ` Ben Evans
2015-09-16 15:16 ` Simmons, James A.
2015-09-16 15:24 ` Patrick Farrell
2015-09-16 16:14 ` Olaf Weber
2015-09-21 9:41 ` Dilger, Andreas
2015-09-21 14:31 ` Ben Evans [this message]
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=D2258CC0.183A%jevans@cray.com \
--to=bevans@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.