From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: arlin.r.davis-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: dapltest and listening endpoints.
Date: Thu, 27 Feb 2014 12:14:57 -0600 [thread overview]
Message-ID: <007f01cf33e7$d28de410$77a9ac30$@opengridcomputing.com> (raw)
In-Reply-To:
> -----Original Message-----
> From: Steve Wise [mailto:swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org]
> Sent: Thursday, February 27, 2014 11:36 AM
> To: 'arlin.r.davis-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org'
> Cc: 'linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org'
> Subject: dapltest and listening endpoints.
>
> Hey Arlin, I'm trying to clean up the dapl/iwarp/cxgb4 issues, and I'm
> seeing something strange. Each time I run a transaction test, I see
that
> listening endpoints are leaked or left around by the dapltest server.
>
> Q: after a completed test, should the dapltest server process have
> destroyed all of its listening endpoints except for the one used to
handle
> the next test? Or does it maybe keep them around and reuse them?
>
Ignore this. My setup was broken.
Sorry for the noise...
--
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
next reply other threads:[~2014-02-27 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 18:14 Steve Wise [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-27 17:35 dapltest and listening endpoints Steve Wise
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='007f01cf33e7$d28de410$77a9ac30$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=arlin.r.davis-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 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.