In the past the we always tried to allocate an fmr_pool
and if it failed on ENOSYS (not supported) then we continued
with dma mr. This is not the case anymore and if we tried to
allocate an fmr_pool then it is supported and we expect to succeed.
Also, the check if fmr_pool is allocated when free i
On Thu, Jul 30, 2015 at 11:06 AM, Sagi Grimberg wrote:
> In the past the we always tried to allocate an fmr_pool
> and if it failed on ENOSYS (not supported) then we continued
> with dma mr. This is not the case anymore and if we tried to
> allocate an fmr_pool then it is supported and we expect t
On 7/30/2015 1:31 PM, Or Gerlitz wrote:
On Thu, Jul 30, 2015 at 11:06 AM, Sagi Grimberg wrote:
In the past the we always tried to allocate an fmr_pool
and if it failed on ENOSYS (not supported) then we continued
with dma mr. This is not the case anymore and if we tried to
allocate an fmr_pool t
On Thu, Jul 30, 2015 at 3:23 PM, Sagi Grimberg wrote:
> Today, iser is not usable with no FRWR and no FMR support. (it once was
> when we bounced to higher-order allocations but we don't do that
> anymore). Memory registration is a requirement support for iser today.
OK, sure, we now have FRWR su
