Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Tom Talpey <tom@talpey.com>
Cc: dhowells@redhat.com, Steve French <sfrench@samba.org>,
	Stefan Metzmacher <metze@samba.org>,
	Paulo Alcantara <pc@manguebit.com>,
	Matthew Wilcox <willy@infradead.org>,
	linux-cifs@vger.kernel.org
Subject: cifs RDMA restrictions
Date: Tue, 01 Apr 2025 17:55:59 +0100	[thread overview]
Message-ID: <563557.1743526559@warthog.procyon.org.uk> (raw)

Hi Tom,

I'm looking at cleaning up the "struct page" instances in smbdirect.c as much
as possible.  Can you tell me what are the restrictions on the size of a
segment attached to an SGE?  For instance, by:

	static bool smb_set_sge(struct smb_extract_to_rdma *rdma,
				struct page *lowest_page, size_t off, size_t len)
	{
		struct ib_sge *sge = &rdma->sge[rdma->nr_sge];
		u64 addr;

		addr = ib_dma_map_page(rdma->device, lowest_page,
				       off, len, rdma->direction);
		if (ib_dma_mapping_error(rdma->device, addr))
			return false;

		sge->addr   = addr;
		sge->length = len;
		sge->lkey   = rdma->local_dma_lkey;
		rdma->nr_sge++;
		return true;
	}

Thanks,
David


             reply	other threads:[~2025-04-01 16:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01 16:55 David Howells [this message]
2025-04-01 18:02 ` cifs RDMA restrictions Tom Talpey
2025-04-01 19:34   ` David Howells
2025-04-02 17:02     ` Tom Talpey
2025-04-02 17:09       ` David Howells
     [not found]         ` <CAH2r5ms2J06tJr4VEVDgmcj_1uqOnhYzbC1ybrMWDm=f8wVDoA@mail.gmail.com>
2025-04-02 18:04           ` Tom Talpey
2025-04-02 19:26             ` David Howells
2025-04-02 19:36               ` Tom Talpey
2025-04-02 19:54                 ` [RFC PATCH] cifs: Collapse smbd_recv_*() into smbd_recv() and just use copy_to_iter() David Howells

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=563557.1743526559@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=metze@samba.org \
    --cc=pc@manguebit.com \
    --cc=sfrench@samba.org \
    --cc=tom@talpey.com \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox