public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Vipul Pandya <vipul-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
To: venkat.x.venkatsubra-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Steve Wise
	<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>,
	Kumar Sanghvi <kumaras-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
Subject: rds_iw_send_ack issue in Fedora14
Date: Tue, 20 Mar 2012 20:49:13 +0530	[thread overview]
Message-ID: <4F689FF1.3030107@chelsio.com> (raw)


Hi Venkat,

We are seeing an issue with rds_iw_send_ack function in Fedora14 OS.

The issue is as follows:
RDS protocol requires to send an acknowledgement back to the sender for
the data it has received. RDS can send that acknowledgment by two ways:
1. It can send a piggyback ack while sending data
2. It can send only ACK packet without any data.

The issue occurs in case 2 above. For sending an ACK only packet RDS
takes another path and different variables and calls rds_iw_attempt_ack
function. This function forms RDS header by putting ACK number in it. It
puts rest of the fields in RDS header as zero. After that it calculates
checksum of that header and puts that checksum also in the header. After
this it calls ib_post_send.

Now the problem is in calculating the checksum. What happens is checksum
gets calculated perfectly fine for the "first time". For the second time
it calculates the checksum as same as first time even though ACK number
is different for the second time. Thus it results into checksum
verification failure on the peer side and connection gets torn down and
receiver request gets flushed. We see "WC Error:  status = 5 opcode = 0"
errors in dmesg on the sender side. I suspect here that it is a dma
mapping or flushing issue.

To be sure that the issue is with rds_iw_send_ack i used the same
sg_list for forming work request in rds_iw_send_ack what is being used
by the rds_iw_xmit. After this issue is resolved. So, i think something
is wrong with the dma mapping in rds_iw_send_ack function.

I only changed the following line in rds_iw_recv_init_ack and it started
working.

-       sge->addr = ic->i_ack_dma;
+       sge->addr = ic->i_send_hdrs_dma;

Interestingly, the issue occurs only on Fedora14(2.6.35.6-45) OS. The
issue does not occur with both RHEL6.0(2.6.32-71.el6.x86_64) and
RHEL6.1(2.6.32-131.el6.x86_64) OS. The RDS module code is similar for
both the OSes.

Can you please share your thoughts?

Thanks,
Vipul Pandya
--
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

                 reply	other threads:[~2012-03-20 15:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F689FF1.3030107@chelsio.com \
    --to=vipul-ut6up61k2wzbdgjk7y7tuq@public.gmane.org \
    --cc=kumaras-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org \
    --cc=venkat.x.venkatsubra-QHcLZuEGTsvQT0dZR+AlfA@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