public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: lihaidong <lihaidong-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Problems using krping
Date: Sun, 24 Jan 2010 21:28:09 -0600	[thread overview]
Message-ID: <4B5D0FC9.6060403@opengridcomputing.com> (raw)
In-Reply-To: <201001251036131874884-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>


>  
> >> Why data transferring happened before server waked up from waiting for 
> >> CONNECTED?
> >This can happen.  There is a race between getting the CONNECTED event 
> >and the first incoming data completion (like a recv completion).
> Could give me some tips to fix this? Since this sometimes will upset 
> normal state machine, which a stable program does not allow it appears.
> --

What normal state machine?  Its the nature of the beast.  Make your 
state machine handle it. :)



--
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

  parent reply	other threads:[~2010-01-25  3:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201001211807011710722@inspur.com>
     [not found] ` <201001211807011710722-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-21 14:40   ` Problems using krping Steve Wise
     [not found] ` <201001221533186875550@inspur.com>
     [not found]   ` <201001221533186875550-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-22 15:16     ` Steve Wise
     [not found]   ` <201001242242553436345@inspur.com>
     [not found]     ` <201001242242553436345-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-24 21:44       ` Steve Wise
     [not found]     ` <201001251036131874884@inspur.com>
     [not found]       ` <201001251036131874884-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-25  3:28         ` Steve Wise [this message]
     [not found]       ` <201001261339589687690@inspur.com>
     [not found]         ` <201001261339589687690-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-26 15:01           ` Steve Wise
     [not found]       ` <201001262046537030587@inspur.com>
     [not found]         ` <201001262046537030587-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-26 15:02           ` 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=4B5D0FC9.6060403@opengridcomputing.com \
    --to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
    --cc=lihaidong-6gUaA8visnnQT0dZR+AlfA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox