All of lore.kernel.org
 help / color / mirror / Atom feed
* fmr pool and remap doubt
@ 2012-04-30 15:56 Parav.Pandit-iH1Dq9VlAzfQT0dZR+AlfA
  0 siblings, 0 replies; only message in thread
From: Parav.Pandit-iH1Dq9VlAzfQT0dZR+AlfA @ 2012-04-30 15:56 UTC (permalink / raw)
  To: linux-rdma-u79uwXL29TY76Z2rM5mHXA
  Cc: ogerlitz-VPRAkNaXOzVWk0Htik3J/w, roland-BHEL68pLQRGGvPXPguhicg,
	Parav.Pandit-iH1Dq9VlAzfQT0dZR+AlfA

Hi,

I am trying to understand remapping functionality and fmr_pool.c.
Looking back at old thread: http://lists.openfabrics.org/pipermail/general/2006-February/017198.html

Can you please confirm whether my understanding is correct or not.
1. max_map_per_fmr  indicates that - different memory pages can be remapped (again) without invoking unmap_fmr().
Basically previous mapping is over-written on every map_phys_fmr() call with new mapping without doing unmapping.

2. adapter indicates above limit - how many times old mapping can be overwritten (remapped) before invoking unmap_fmr().

3. Remapping allows faster operation compare to map(), unmap() sequence, due to which unmap_fmr() is mostly done in worker threads in SDP, RDS etc consumers.

Is above understanding correct?

Regards,
Parav Pandit

--
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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2012-04-30 15:56 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-04-30 15:56 fmr pool and remap doubt Parav.Pandit-iH1Dq9VlAzfQT0dZR+AlfA

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.