From: "Todd Strader" <tstrader-YJJp1DzrooEAvxtiuMwx3w@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: ConnectX WQE invalidation
Date: Tue, 23 Feb 2010 17:11:36 -0600 [thread overview]
Message-ID: <4B8460A8.3000203@exegy.com> (raw)
Hi,
I've posted this question to the Mellanox support site, but I've found
that it's not terribly responsive. I was hoping someone here would know
the answer to my question, or be able to direct me to someone who does.
I'm reading section 9.2.1 of the ConnectX Family PRM (Posting a Work
Request to a Send Work Queue) and I'm a little confused.
Previous sections mention that the Send Queue is sampled at the WQEBB
boundaries. And ownership is passed from SW to HW via the owner bit in
the Ctrl segment. If that is the case, why does each 64 byte block of
the SQ need to be invalidated initially and as the SQ progresses?
Let's say my WQEBB is 256 bytes. I would think that the HCA would only
sample every 256 bytes for a valid control structure. Why do I need to
maintain 64 byte chunks?
Thanks for the help.
Todd Strader
This e-mail and any documents accompanying it may contain legally privileged and/or confidential information belonging to Exegy, Inc. Such information may be protected from disclosure by law. The information is intended for use by only the addressee. If you are not the intended recipient, you are hereby notified that any disclosure or use of the information is strictly prohibited. If you have received this e-mail in error, please immediately contact the sender by e-mail or phone regarding instructions for return or destruction and do not use or disclose the content to others.
--
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:[~2010-02-23 23:11 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=4B8460A8.3000203@exegy.com \
--to=tstrader-yjjp1dzrooeavxtiumwx3w@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