> -----Original Message----- > From: linux-rdma-owner@xxxxxxxxxxxxxxx [mailto:linux-rdma- > owner@xxxxxxxxxxxxxxx] On Behalf Of Sagi Grimberg > Sent: Thursday, July 20, 2017 10:18 AM > To: Ursula Braun <ubraun@xxxxxxxxxxxxxxxxxx>; linux-rdma@xxxxxxxxxxxxxxx > Cc: hch@xxxxxx; schwidefsky@xxxxxxxxxx; heiko.carstens@xxxxxxxxxx; > hwippel@xxxxxxxxxxxxxxxxxx; raspl@xxxxxxxxxxxxxxxxxx > Subject: Re: [RFC net-next 05/10] net/smc: register RMB-related memory region > > > A memory region created for a new RMB must be registered explicitly, > > before the peer can make use of it for remote DMA transfer. > > OK, Now I understand the sgl construction in the previous patch. > > We got rid of the synchronous memory registration API in the kernel in the > absence of users, but now with smc we might want to restore it because looking > at the patchset, the fast memory registration scheme is obviously not a good fit. > > For the simple smc use case the API should be as simple as: > > ib_reg_contig_mr(struct ib_pd *pd, void *addr, size_t length); > > Do you have a use-case for scattered buffers memory registration? sendmsg() call msghdr->msg_iov array can represent non page aligned memory vectors, that can be transmitted without doing any copy in kernel? ��.n��������+%������w��{.n�����{���fk��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
