All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] dlm: fix lowcomms_connect_node for sctp
Date: Fri, 18 Sep 2009 16:37:54 -0500	[thread overview]
Message-ID: <20090918213754.GA18138@redhat.com> (raw)
In-Reply-To: <20090918193906.GB4340@redhat.com>

On Fri, Sep 18, 2009 at 02:39:06PM -0500, David Teigland wrote:
> The recently added dlm_lowcomms_connect_node() from
> 391fbdc5d527149578490db2f1619951d91f3561 does not work
> when using SCTP instead of TCP.  The sctp connection code
> has nothing to do without data to send.  Check for no data
> in the sctp connection code and do nothing instead of
> triggering a BUG.  Also have connect_node() do nothing
> when the protocol is sctp.

With this patch I can use sctp (single interface), but I'm getting these
alloc_fd errors (which seem harmless enough) have you seen them before?

Also, gfs is *really* slow using sctp!

dlm: Using SCTP for communications
SCTP: Hash tables configured (established 58254 bind 58254)
dlm: foo: joining the lockspace group...
dlm: got new/restarted association 1 nodeid 4
dlm: foo: group event done 0 0
dlm: foo: recover 1
dlm: foo: add member 5
dlm: foo: add member 4
dlm: foo: add member 2
dlm: Initiating association with node 2
alloc_fd: slot 0 not NULL!
dlm: got new/restarted association 2 nodeid 2
dlm: foo: join complete
GFS2: fsid=bull:foo.2: Joined cluster. Now mounting FS...
dlm: foo: total members 3 error 0
dlm: foo: dlm_recover_directory
dlm: foo: dlm_recover_directory 13 entries



  reply	other threads:[~2009-09-18 21:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18 19:39 [Cluster-devel] [PATCH] dlm: fix lowcomms_connect_node for sctp David Teigland
2009-09-18 21:37 ` David Teigland [this message]
2009-09-21  8:50   ` Christine Caulfield

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=20090918213754.GA18138@redhat.com \
    --to=teigland@redhat.com \
    /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.