From: Sagi Grimberg <sagig-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH, RFC] rdma: split struct ib_send_wr
Date: Tue, 4 Aug 2015 20:06:16 +0300 [thread overview]
Message-ID: <55C0F108.4090003@dev.mellanox.co.il> (raw)
In-Reply-To: <1438672609-12599-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
On 8/4/2015 10:16 AM, Christoph Hellwig wrote:
> This patch split up struct ib_send_wr so that all non-trivial verbs
> use their own structure which embedds struct ib_send_wr. This dramaticly
> shrinks the size of a WR for most common operations.
Hey Christoph,
I think this looks good in general.
Question though, a ULP may want to keep a couple of WRs around instead
of having each allocated in the stack and handled one by one. We need
to provide it with a hint of what is the size it needs.
I just posted a patch to do that in iser
(http://www.spinics.net/lists/linux-rdma/msg27632.html).
So if I would want to preallocate an array of work requests, what is the
size of the space I'd need?
is it some form of max(sizeof(struct ib_send_wr),
sizeof(struct ib_fastreg_wr),
sizeof(struct sig_handover), ..)?
>
> This is just a WIP with basic testing for now. While all in-tree drivers
> except for iSER and iSERt are converted testing coverage is very limited.
>
> For iSER I could really use a helping hand as the WR usage is rather
> confusing..
I can do it. no problem.
--
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
next parent reply other threads:[~2015-08-04 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1438672609-12599-1-git-send-email-hch@lst.de>
[not found] ` <1438672609-12599-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-08-04 17:06 ` Sagi Grimberg [this message]
[not found] ` <55C0F108.4090003-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-08-04 17:23 ` [PATCH, RFC] rdma: split struct ib_send_wr Christoph Hellwig
[not found] ` <20150804172328.GA22468-jcswGhMUV9g@public.gmane.org>
2015-08-04 17:44 ` Sagi Grimberg
[not found] ` <55C0F9FA.6060105-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-08-04 17:47 ` Christoph Hellwig
[not found] ` <20150804174720.GA22895-jcswGhMUV9g@public.gmane.org>
2015-08-04 17:54 ` Sagi Grimberg
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=55C0F108.4090003@dev.mellanox.co.il \
--to=sagig-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=hch-jcswGhMUV9g@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.