Re: [PATCH 2/2] iw_cxgb4: add fast-path for small REG_MR operations

2016-09-18 Thread Leon Romanovsky
On Sun, Sep 18, 2016 at 07:40:29PM -0500, Steve Wise wrote: > > 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

RE: [PATCH 2/2] iw_cxgb4: add fast-path for small REG_MR operations

2016-09-18 Thread Steve Wise
> 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

Re: [PATCH 2/2] iw_cxgb4: add fast-path for small REG_MR operations

2016-09-18 Thread Leon Romanovsky
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 do

[PATCH 2/2] iw_cxgb4: add fast-path for small REG_MR operations

2016-09-16 Thread Steve Wise
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