> So you want the page size specified in the fast_reg_page_list as
> opposed to when the page list is bound to the fast_reg mr (via
> post_send)?
It's kind of the same thing, since the fast_reg_page_list is part of the
send work request... the structures you have at the moment are:
> + struct {
> + u64 iova_start;
> + struct ib_fast_reg_page_list *page_list;
> + int fbo;
> + u32 length;
> + int access_flags;
> + struct ib_mr *mr;
(side note... move this pointer up with the other pointers, so you don't
end up with a hole in the structure due to alignment... or stick an int
page_size in to fill the hole)
> + } fast_reg;
> +struct ib_fast_reg_page_list {
> + struct ib_device *device;
> + u64 *page_list;
> + int page_list_len;
> +};
is page_list_len the maximum length of the page_list, or is it filled in
by the consumer? The driver could figure out the length of the
page_list for any given work request by looking at the MR length and the
page_size I suppose.
- R.
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
