From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 09/11 v2] RDMA/cxgb4: Support on-chip SQs.
Date: Tue, 28 Sep 2010 20:41:24 -0700 [thread overview]
Message-ID: <adatyl943ob.fsf@cisco.com> (raw)
In-Reply-To: <4CA22E84.404-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org> (Steve Wise's message of "Tue, 28 Sep 2010 13:05:56 -0500")
> We would remove it I guess. I see that mlx4 assumes
> pgprot_writecombine() exists and works correctly across all platforms.
> See mlx4_ib_mmap().
It might be more accurate to say that mlx4 assumes pgprot_writecombine()
is defined on all platforms. Any platform that hasn't defined it (or
where the concept of write combining doesn't make sense) just falls back
to defining it as pgprot_noncached().
>From a quick grep it seems that /arch/powerpc has no definition of
pgprot_writecombine() but your code seems to say that one could be
given.
> If all platforms support pgprot_writecombine() correctly, then we
> don't need ocqp_supported().
As I said, it's a bit tricky. All platforms get some definition of
pgprot_writecombine(), but some platforms might define it as just giving
a non-cached mapping, which might lead to dire performance (perhaps
worse than just putting the SQ in host memory). I'm not sure what the
best way to handle it is -- I suppose if you wanted to get fancy you
could do a quick benchmark on startup (if such a thing is possible).
- R.
--
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 prev parent reply other threads:[~2010-09-29 3:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 16:23 [PATCH 09/11 v2] RDMA/cxgb4: Support on-chip SQs Steve Wise
[not found] ` <20100913162357.20948.28267.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2010-09-28 17:57 ` Roland Dreier
[not found] ` <adad3rx699s.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2010-09-28 18:05 ` Steve Wise
[not found] ` <4CA22E84.404-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-09-29 3:41 ` Roland Dreier [this message]
[not found] ` <adatyl943ob.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2010-09-29 17:14 ` Steve Wise
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=adatyl943ob.fsf@cisco.com \
--to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox