From: frank zago <fzago-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: ib_post_send in drivers
Date: Fri, 20 Nov 2009 10:16:42 -0600 [thread overview]
Message-ID: <4B06C0EA.2070501@systemfabricworks.com> (raw)
Hello,
It seems ib_post_send() is implemented slightly differently in the
various hardware drivers (as in kernel 2.6.31). Here are the differences
I've noticed regarding the bad_wr parameter.
amso1100/c2_qp.c : c2_post_send()
* bails out and does not set bad_wr if the 1st check is bad.
cxgb3/iwch_qp.c : post_one_send()
* test for bad_send_wr but it should always be set
cxgb3/iwch_qp.c : iwch_post_send()
* bails out and does not set bad_wr if the 1st 2 checks are bad
ehca/ehca_reqs.c : ehca_post_send()
* bails out and does not set bad_wr if the 1st check is bad.
* test for bad_send_wr but it should always be set
* always return success if at least one post succeeded.
ehca/ehca_reqs.c : post_one_send()
* test for bad_send_wr but it should always be set
nes/nes_verbs.c : nes_post_send()
* bails out and does not set bad_wr if the 1st check is bad.
I think assume most are bugs (especially the ehca driver). I can post a
patch to fix these if confirmed.
Regards,
Frank
--
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:[~2009-11-20 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 16:16 frank zago [this message]
[not found] ` <4B06C0EA.2070501-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
2009-11-20 19:26 ` ib_post_send in drivers Bart Van Assche
[not found] ` <e2e108260911201126o5233ea3v94163083fe3d26fc-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-20 20:08 ` Sean Hefty
[not found] ` <E102E8F5252B43318544B660CF6B78F7-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-11-21 11:17 ` Bart Van Assche
[not found] ` <e2e108260911210317t323adfe0k4aa3e821d3a1c63c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-21 20:01 ` Jason Gunthorpe
[not found] ` <20091121200128.GD1966-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2009-11-21 20:37 ` Bart Van Assche
[not found] ` <e2e108260911211237j2b9fd96cn3df78fe5c59fdc5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-21 21:52 ` Jason Gunthorpe
2009-11-23 19:09 ` Roland Dreier
2009-11-23 19:02 ` Roland Dreier
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=4B06C0EA.2070501@systemfabricworks.com \
--to=fzago-klaocwyjdxkshymvu7je4pqqe7ycjdx5@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