From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Tom Tucker <tom@opengridcomputing.com>, linux-nfs@vger.kernel.org
Subject: Re: FW: [PATCH for 2.6.25] SVCRDMA: Use only 1 RDMA read scatter entry for iWARP adapters
Date: Mon, 24 Mar 2008 09:57:04 -0700 [thread overview]
Message-ID: <adave3crrfj.fsf@cisco.com> (raw)
In-Reply-To: <20080324154452.GA23736@fieldses.org> (J. Bruce Fields's message of "Mon, 24 Mar 2008 11:44:52 -0400")
> Will do, thanks, but, as a subsequent patch, could we clean this up a
> little? For example, assuming sge_count and sc_max_sge are always
> positive, isn't the (sge_count > 1) check superfluous, given that the
> following min_t's going to produce 1 in that case anyway?
Yes, I had the same thought reading the code but I didn't want to try
and do too many things in one patch.
> Also, would it be possible just to ensure sc_max_sge is just set to 1
> from the start in this case?
I think the problem with this is that on InfiniBand, it is fine to
have multiple scatter entries for an RDMA read request, while on iWARP
only 1 scatter entry is possible for RDMA read. For both IB and
iWARP, you can eg have multiple gather entries for an RDMA write. So
sc_max_sge as it stands may want to be bigger than 1 even for iWARP devices.
One not-too-bad possibility would just be to have sc_max_sge and
sc_max_sge_rdma_read fields and initialize them properly based on IB
vs iWARP...
- R.
next prev parent reply other threads:[~2008-03-24 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 21:27 [PATCH for 2.6.25] SVCRDMA: Use only 1 RDMA read scatter entry for iWARP adapters Roland Dreier
[not found] ` <adaiqzdt9lb.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2008-03-23 23:52 ` Tom Tucker
2008-03-24 3:06 ` FW: " Tom Tucker
2008-03-24 15:44 ` J. Bruce Fields
2008-03-24 16:57 ` Roland Dreier [this message]
[not found] ` <adave3crrfj.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2008-03-24 17:05 ` J. Bruce Fields
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=adave3crrfj.fsf@cisco.com \
--to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tom@opengridcomputing.com \
/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