public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org,
	jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org
Subject: [PATCH 0/1] infiniband-diags: add rdma-ndd daemon
Date: Thu, 30 Oct 2014 19:54:29 -0400	[thread overview]
Message-ID: <1414713270-12710-1-git-send-email-ira.weiny@intel.com> (raw)

This is the follow on patch to the kernel series which changes the default Node
Description to be "<hostname> <device>"

This patch adds support for a "RDMA Node Description Daemon" (rdma-ndd) which
uses the new poll support of the procfs hostname file to monitor for changes to
the hostname and updates the Node Descriptions appropriately.  Both the kernel
changes and the user space daemon are necessary to ensure that the Node
Description in the SMA and SA reflect the hostname/device in all cases if the
device supports traps and the SM either responds to those traps or polls for
the Node Description periodically.  This is true for the following reasons.

	1) No matter when the drivers are loaded they will return
	   "<hostname> <device>" to the SM when initially queried.
	2) If the hostname is not set when the driver is loaded (as is
	   likely at boot) subsequent sets of hostname (from any source
	   including dhclient) will trigger the daemon to update all node
	   descriptions.  The use of dhclient hooks is not sufficient to handle
	   user invoked hostname changes.
	3) If the daemon is started after the hostname has changed it starts by
	   writing the hostname to the Node Descriptions sysfs files which will
	   trigger the devices to send a trap to the SM.

Thus the drivers, any automated set of the hostname (such as DHCP), and the
rdma-ndd daemon can be started in any order and the SMA will reflect the
hostname properly.


[PATCH] infiniband-diags: add rdma-ndd daemon
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2014-10-30 23:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 23:54 ira.weiny-ral2JQCrhuEAvxtiuMwx3w [this message]
     [not found] ` <1414713270-12710-1-git-send-email-ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-10-30 23:54   ` [PATCH] infiniband-diags: add rdma-ndd daemon ira.weiny-ral2JQCrhuEAvxtiuMwx3w
     [not found]     ` <1414713270-12710-2-git-send-email-ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-10-31  6:58       ` Bart Van Assche
     [not found]         ` <54533318.8010700-HInyCGIudOg@public.gmane.org>
2014-10-31  9:24           ` Weiny, Ira
     [not found]             ` <2807E5FD2F6FDA4886F6618EAC48510E0CB79457-8k97q/ur5Z2krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-10-31  9:32               ` Bart Van Assche
     [not found]                 ` <54535741.3030409-HInyCGIudOg@public.gmane.org>
2014-10-31  9:43                   ` Weiny, Ira
2014-11-08  0:40       ` Jason Gunthorpe
     [not found]         ` <20141108004029.GB12120-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2014-11-10  0:28           ` Weiny, Ira
     [not found]             ` <2807E5FD2F6FDA4886F6618EAC48510E0CBA8FCD-8k97q/ur5Z2krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-11-10  5:11               ` Jason Gunthorpe
     [not found]                 ` <20141110051155.GD31256-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2014-11-10 18:32                   ` Weiny, Ira
     [not found]                     ` <2807E5FD2F6FDA4886F6618EAC48510E0CBB39E8-8k97q/ur5Z2krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-11-10 19:05                       ` Jason Gunthorpe
2014-11-11 15:11                       ` Hal Rosenstock

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=1414713270-12710-1-git-send-email-ira.weiny@intel.com \
    --to=ira.weiny-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
    --cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox