All of lore.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
To: Eldad Zinger <eldadz-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: CMA handler status code
Date: Tue, 27 Jul 2010 09:40:30 +0300	[thread overview]
Message-ID: <4C4E7F5E.6070306@Voltaire.com> (raw)
In-Reply-To: <AANLkTik2eOWELUAwjL+tfjMb28L3OjWB57iMyvDpOWDm-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Eldad Zinger wrote:
> event.status = ib_event->param.sidr_rep_rcvd.status
> event.status = ib_event->param.rej_rcvd.reason
> event.status should be 0 for success, or negative value of generic error code.
> In that code, the error code is positive and do not comply with generic error code.

Basically, I believe that the status equals reject reason for rdma-cm reject event
is known to the kernel developers that deal with the rdma-cm. Personally, I'm fine
with it, we could document that, but currently there's no rdma-cm document under 
Documentation/infiniband which could have this.

For user space, I would add a comment in the man pages

> In order to make the status field available for other modules (like
> SDP), that field should be format-consistent.

With SDP being out of tree for about four-six years (and counting), somehow
hard to take into account claims related to it.

Ot.
--
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-07-27  6:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27  4:34 CMA handler status code Eldad Zinger
     [not found] ` <AANLkTik2eOWELUAwjL+tfjMb28L3OjWB57iMyvDpOWDm-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-27  6:40   ` Or Gerlitz [this message]
     [not found]     ` <4C4E7F5E.6070306-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-07-27  6:48       ` Or Gerlitz
2010-07-27  8:11   ` Hefty, Sean
     [not found]     ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25A8D7FBFB-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-07-29  6:38       ` Or Gerlitz
     [not found]         ` <4C5121D7.7070604-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-07-29 16:58           ` Hefty, Sean
2010-07-29 21:37           ` [PATCH] librdmacm: document event status field Hefty, Sean

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=4C4E7F5E.6070306@Voltaire.com \
    --to=ogerlitz-hkgkho2ms0fwk0htik3j/w@public.gmane.org \
    --cc=eldadz-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@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.