From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Cc: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
roid-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
oren-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH for-3.11 7/7] IB/iser: Introduce fast memory registration model (FRWR)
Date: Mon, 22 Jul 2013 13:46:22 +0200 [thread overview]
Message-ID: <51ED1B8E.7070703@acm.org> (raw)
In-Reply-To: <1374153931-7313-8-git-send-email-ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On 07/18/13 15:25, Or Gerlitz wrote:
> +static int iser_fast_reg_mr(struct fast_reg_descriptor *desc,
> + struct iser_conn *ib_conn,
> + struct iser_regd_buf *regd_buf,
> + u32 offset, unsigned int data_size,
> + unsigned int page_list_len)
> +{
> + struct ib_send_wr fastreg_wr, inv_wr;
> + struct ib_send_wr *bad_wr, *wr = NULL;
> + u8 key;
> + int ret;
> +
> + if (!desc->valid) {
> + memset(&inv_wr, 0, sizeof(inv_wr));
> + inv_wr.opcode = IB_WR_LOCAL_INV;
> + inv_wr.send_flags = IB_SEND_SIGNALED;
> + inv_wr.ex.invalidate_rkey = desc->data_mr->rkey;
> + wr = &inv_wr;
> + /* Bump the key */
> + key = (u8)(desc->data_mr->rkey & 0x000000FF);
> + ib_update_fast_reg_key(desc->data_mr, ++key);
> + }
> +
> + /* Prepare FASTREG WR */
> + memset(&fastreg_wr, 0, sizeof(fastreg_wr));
> + fastreg_wr.opcode = IB_WR_FAST_REG_MR;
> + fastreg_wr.send_flags = IB_SEND_SIGNALED;
> + fastreg_wr.wr.fast_reg.iova_start = desc->data_frpl->page_list[0] + offset;
> + fastreg_wr.wr.fast_reg.page_list = desc->data_frpl;
> + fastreg_wr.wr.fast_reg.page_list_len = page_list_len;
> + fastreg_wr.wr.fast_reg.page_shift = SHIFT_4K;
> + fastreg_wr.wr.fast_reg.length = data_size;
> + fastreg_wr.wr.fast_reg.rkey = desc->data_mr->rkey;
> + fastreg_wr.wr.fast_reg.access_flags = (IB_ACCESS_LOCAL_WRITE |
> + IB_ACCESS_REMOTE_WRITE |
> + IB_ACCESS_REMOTE_READ);
Hello Sagi,
If I interpret the above code correctly the rkey used in the previous
FRWR is invalidated as soon as a new FRWR is queued. Does this mean that
the iSER initiator limits queue depth to one ?
Another question: is it on purpose that iscsi_iser_cleanup_task() does
not invalidate an rkey if a command has been aborted successfully ? A
conforming iSER target does not send a response for aborted commands.
Will successful command abortion result in the rkey not being
invalidated ? What will happen if a new FRWR is submitted with an rkey
that is still valid ?
Thanks,
Bart.
--
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 prev parent reply other threads:[~2013-07-22 11:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 13:25 [PATCH for-3.11 0/7] Add Fast-Reg support to the iser initiator driver Or Gerlitz
[not found] ` <1374153931-7313-1-git-send-email-ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-07-18 13:25 ` [PATCH for-3.11 1/7] IB/iser: Use proper debug level value for info prints Or Gerlitz
2013-07-18 13:25 ` [PATCH for-3.11 2/7] IB/iser: Restructure allocation/deallocation of connection resources Or Gerlitz
2013-07-18 13:25 ` [PATCH for-3.11 3/7] IB/iser: Accept session->cmds_max from user space Or Gerlitz
2013-07-18 13:25 ` [PATCH for-3.11 4/7] IB/iser: Generalize rdma memory registration Or Gerlitz
2013-07-18 13:25 ` [PATCH for-3.11 5/7] IB/iser: Handle unaligned SG in separate function Or Gerlitz
2013-07-18 13:25 ` [PATCH for-3.11 6/7] IB/iser: Place the fmr pool into a union in iser's IB conn struct Or Gerlitz
2013-07-18 13:25 ` [PATCH for-3.11 7/7] IB/iser: Introduce fast memory registration model (FRWR) Or Gerlitz
[not found] ` <1374153931-7313-8-git-send-email-ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-07-22 11:46 ` Bart Van Assche [this message]
[not found] ` <51ED1B8E.7070703-HInyCGIudOg@public.gmane.org>
2013-07-22 13:11 ` Sagi Grimberg
[not found] ` <51ED2F97.2080400-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-07-23 11:58 ` Bart Van Assche
[not found] ` <51EE6FFE.8040802-HInyCGIudOg@public.gmane.org>
2013-07-23 14:21 ` Or Gerlitz
[not found] ` <CAJZOPZ+1TLQ-vwsZG8dgxhP332CQeDNOWfzGRdTbwRxLRhL95w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-23 14:47 ` Bart Van Assche
[not found] ` <51EE9773.9050003-HInyCGIudOg@public.gmane.org>
2013-07-24 16:47 ` Or Gerlitz
[not found] ` <51F000CB.3050808@mellanox.com>
[not found] ` <51F000CB.3050808-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-07-26 9:27 ` Bart Van Assche
2013-07-23 14:33 ` Sagi Grimberg
2013-07-22 14:37 ` Or Gerlitz
2013-07-26 17:15 ` Vu Pham
[not found] ` <51F2AEB6.6090000-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-07-28 8:15 ` Or Gerlitz
[not found] ` <51F4D305.7090700-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-07-28 9:26 ` Sagi Grimberg
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=51ED1B8E.7070703@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=oren-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=roid-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sagig-VPRAkNaXOzVWk0Htik3J/w@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