hail-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: [hail patch 3/7] Drop useless code from cldu.c
Date: Thu, 29 Jul 2010 20:50:03 -0600	[thread overview]
Message-ID: <20100729205003.1cc235a1@lembas.zaitcev.lan> (raw)

Forgot to kill this when <StorageNode> was removed.

Signed-off-by: Pete Zaitcev <zaitcev@redhat.com>

---
 server/cldu.c |   23 -----------------------
 1 file changed, 23 deletions(-)

commit 8945b6d9da4efb3fc3f8bd33759c85ee57b148dd
Author: Pete Zaitcev <zaitcev@yahoo.com>
Date:   Thu Jul 29 19:24:17 2010 -0600

    StorageNode is gone, but this chunk was forgotten.

diff --git a/server/cldu.c b/server/cldu.c
index e247f45..5f3631b 100644
--- a/server/cldu.c
+++ b/server/cldu.c
@@ -351,29 +351,6 @@ static int cldu_set_cldc(struct cld_session *sp, int newactive)
 
 	ncld_read_free(nrp);
 
-	/*
-	 * If configuration gives us storage nodes, we shortcut scanning
-	 * of CLD, because:
-	 *  - the scanning may fail, and we should not care
-	 *  - NIDs for configured nodes are auto-assigned and may conflict
-	 * This will go away with the demise of <StorageNode>.
-	 */
-	if (tabled_srv.num_stor) {
-		if (debugging)
-			applog(LOG_DEBUG, "Trying to open %d storage nodes",
-			       tabled_srv.num_stor);
-		while (stor_update_cb() < 1) {
-			tm.tv_sec = 3;
-			tm.tv_nsec = 0;
-			nanosleep(&tm, NULL);
-			if (debugging)
-				applog(LOG_DEBUG,
-				       "Trying to reopen %d storage nodes",
-				       tabled_srv.num_stor);
-		}
-		return 0;
-	}
-
 	return 0;
 
 err_dread:

                 reply	other threads:[~2010-07-30  2:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100729205003.1cc235a1@lembas.zaitcev.lan \
    --to=zaitcev@redhat.com \
    --cc=hail-devel@vger.kernel.org \
    --cc=jeff@garzik.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).