From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Leon Romanovsky' <leonro-2ukJVAZIZ/Y@public.gmane.org>
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [PATCH 2/2] iw_cxgb4: add fast-path for small REG_MR operations
Date: Sun, 18 Sep 2016 19:40:29 -0500 [thread overview]
Message-ID: <0bd501d2120e$6bf5aaf0$43e100d0$@opengridcomputing.com> (raw)
In-Reply-To: <20160918142242.GJ2923-2ukJVAZIZ/Y@public.gmane.org>
> On Fri, Sep 16, 2016 at 07:54:52AM -0700, Steve Wise wrote:
> > When processing a REG_MR work request, if fw supports the
> > FW_RI_NSMR_TPTE_WR work request, and if the page list for this
> > registration is <= 2 pages, and the current state of the mr is INVALID,
> > then use FW_RI_NSMR_TPTE_WR to pass down a fully populated TPTE for
> FW
> > to write. This avoids FW having to do an async read of the TPTE
blocking
> > the SQ until the read completes.
> >
> > To know if the current MR state is INVALID or not, iw_cxgb4 must track
the
> > state of each fastreg MR. The c4iw_mr struct state is updated as REG_MR
> > and LOCAL_INV WRs are posted and completed, when a reg_mr is
> destroyed,
> > and when RECV completions are processed that include a local
invalidation.
> >
> > This optimization increases small IO IOPS for both iSER and NVMF.
> >
> > Signed-off-by: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
> > ---
>
> <...>
>
> > + struct ib_reg_wr *wr, struct c4iw_mr *mhp,
> > + u8 *len16)
> > +{
> > + __be64 *p = (__be64 *)fr->pbl;
> > +
> > + fr->r2 = cpu_to_be32(0);
>
> Is there any difference between the line above and "fr->r2 = 0"?
It makes sparse happy, IIRC...
--
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
WARNING: multiple messages have this Message-ID (diff)
From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: "'Leon Romanovsky'" <leonro-2ukJVAZIZ/Y@public.gmane.org>
Cc: <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
<davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: RE: [PATCH 2/2] iw_cxgb4: add fast-path for small REG_MR operations
Date: Sun, 18 Sep 2016 19:40:29 -0500 [thread overview]
Message-ID: <0bd501d2120e$6bf5aaf0$43e100d0$@opengridcomputing.com> (raw)
In-Reply-To: <20160918142242.GJ2923-2ukJVAZIZ/Y@public.gmane.org>
> On Fri, Sep 16, 2016 at 07:54:52AM -0700, Steve Wise wrote:
> > When processing a REG_MR work request, if fw supports the
> > FW_RI_NSMR_TPTE_WR work request, and if the page list for this
> > registration is <= 2 pages, and the current state of the mr is INVALID,
> > then use FW_RI_NSMR_TPTE_WR to pass down a fully populated TPTE for
> FW
> > to write. This avoids FW having to do an async read of the TPTE
blocking
> > the SQ until the read completes.
> >
> > To know if the current MR state is INVALID or not, iw_cxgb4 must track
the
> > state of each fastreg MR. The c4iw_mr struct state is updated as REG_MR
> > and LOCAL_INV WRs are posted and completed, when a reg_mr is
> destroyed,
> > and when RECV completions are processed that include a local
invalidation.
> >
> > This optimization increases small IO IOPS for both iSER and NVMF.
> >
> > Signed-off-by: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
> > ---
>
> <...>
>
> > + struct ib_reg_wr *wr, struct c4iw_mr *mhp,
> > + u8 *len16)
> > +{
> > + __be64 *p = (__be64 *)fr->pbl;
> > +
> > + fr->r2 = cpu_to_be32(0);
>
> Is there any difference between the line above and "fr->r2 = 0"?
It makes sparse happy, IIRC...
--
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:[~2016-09-19 0:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 14:54 [PATCH 0/2] cxgb4 FR_NSMR_TPTE_WR support Steve Wise
2016-09-16 14:54 ` [PATCH 1/2] cxgb4: advertise support for FR_NSMR_TPTE_WR Steve Wise
[not found] ` <cover.1474037695.git.swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2016-09-16 14:54 ` [PATCH 2/2] iw_cxgb4: add fast-path for small REG_MR operations Steve Wise
2016-09-18 14:22 ` Leon Romanovsky
[not found] ` <20160918142242.GJ2923-2ukJVAZIZ/Y@public.gmane.org>
2016-09-19 0:40 ` Steve Wise [this message]
2016-09-19 0:40 ` Steve Wise
2016-09-19 3:28 ` Leon Romanovsky
2016-09-19 5:16 ` [PATCH 0/2] cxgb4 FR_NSMR_TPTE_WR support David Miller
[not found] ` <20160919.011633.1357649774235825501.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2016-09-19 14:17 ` Steve Wise
2016-09-19 14:17 ` Steve Wise
2016-09-19 14:29 ` David Miller
[not found] ` <20160919.102920.1126387243122900012.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2016-09-27 22:03 ` Steve Wise
2016-09-27 22:03 ` Steve Wise
2016-10-03 14:50 ` Doug Ledford
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='0bd501d2120e$6bf5aaf0$43e100d0$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leonro-2ukJVAZIZ/Y@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-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.