From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 09/11 v2] RDMA/cxgb4: Support on-chip SQs.
Date: Wed, 29 Sep 2010 12:14:54 -0500 [thread overview]
Message-ID: <4CA3740E.9020104@opengridcomputing.com> (raw)
In-Reply-To: <adatyl943ob.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
On 09/28/2010 10:41 PM, Roland Dreier wrote:
> > 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.
>
>
This came from the ofed version of mlx4. I assume it works. :)
> > 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).
>
>
oof. I don't want to get that fancy. :)
Seems like what I need is an arch-specific function that indicates if
write combining is supported or not. Or leave the code as-is.
Steve.
--
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
prev parent reply other threads:[~2010-09-29 17:14 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
[not found] ` <adatyl943ob.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2010-09-29 17:14 ` Steve Wise [this message]
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=4CA3740E.9020104@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@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.