From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] RDMA/cxgb3: fail get_dma_mr if the memory footprint can exceed 32b
Date: Fri, 24 Jul 2015 10:44:53 -0400 [thread overview]
Message-ID: <55B24F65.5040103@redhat.com> (raw)
In-Reply-To: <00d501d0c599$84afdb50$8e0f91f0$@opengridcomputing.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On 07/23/2015 06:47 PM, Steve Wise wrote:
>> -----Original Message----- From: Doug Ledford
>> Should this be a static check of the pointer size versus installed
>> memory? Would it be possible to have this work for machines with
>> less than 4GB of physical memory even if they have 64bit pointers,
>> or are you concerned that hotplug memory could take us over the
>> limit after registration and cause problems?
>
> NFSRDMA doesn't need dma-mrs for T3 since it has FRMR + local dma
> lkey support. And since the deficiency really can cause problems on
> 64b systems if the memory grows > 4GB after dma-mr allocation, I
> decided to just not allow them for potential large memory systems.
Ok. I've pulled this for 4.2-rc then.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2015-07-24 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 19:14 [PATCH] RDMA/cxgb3: fail get_dma_mr if the memory footprint can exceed 32b Steve Wise
[not found] ` <20150722191417.9306.17387.stgit-PBeJgSbIpn97NCTnQtmixQ@public.gmane.org>
2015-07-23 21:32 ` Doug Ledford
[not found] ` <55B15D7D.3090601-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-07-23 22:47 ` Steve Wise
2015-07-24 14:44 ` Doug Ledford [this message]
[not found] ` <55B24F65.5040103-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-07-24 14:50 ` Steve Wise
2015-07-24 14:55 ` Doug Ledford
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=55B24F65.5040103@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@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 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.