[Lustre-devel] discontiguous kiov pages
nic at cray.com
Wed Jun 8 09:08:47 PDT 2011
On 06/07/2011 06:57 PM, Oleg Drokin wrote:
>>> It used to be that only the first and last page in an IOV were allowed
>>> to be of a offset + length< PAGE_SIZE.
>> Quite correct. LNDs have relied on this for years now.
>> A change like this should not have occurred without discussion
>> about the wider impact.
> Actually now that we found what's happening, I think the issue is a bit less clear-cut.
> What happens here is the client is submitting two niobufs that are not contiguous.
> As such I see no reason why they need to be contiguous in VM too. Sure the 1.8 way of handling
> this situation was to send separate RPCs, but I think even if two RDMA descriptors need to be
> made, we still save plenty of overhead to justify this.
> (basically we send three niobufs in this case: file pages 0-1, 40-47 (the 47th one is partial) and 49 (full) ).
Oleg - it isn't clear to me what fix you are suggesting here. Are you
saying LNet/LNDs should handle this situation (partial internal page)
under the covers by setting up multiple RDMA on their own? This sounds
like an LND API change, requiring a fix and validation for every LND. I
*think* we might end up violating LNet layering here by having to adjust
internal LNet structures from the LND to make sure the 2nd and
subsequent RDMA landed at the correct spot in the MD, etc.
At least for our network, and I'd venture a guess for others, there is
no way to handle the partial page other than multiple RDMA at the LND
layer. When mapping these pages for RDMA, the internal hole can't be
handled as we just map a set of physical pages for the HW to read
from/write into with a single (address,length) vector. The internal hole
would be ignored and would end up corrupting data as we overwrite the hole.
More information about the lustre-devel