All of lore.kernel.org
 help / color / mirror / Atom feed
From: liweihang <liweihang@huawei.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: "leon@kernel.org" <leon@kernel.org>,
	"dledford@redhat.com" <dledford@redhat.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"linuxarm@openeuler.org" <linuxarm@openeuler.org>
Subject: Re: [PATCH RFC rdma-core 0/5] libhns: Add support for Dynamic Context Attachment
Date: Tue, 23 Feb 2021 08:07:57 +0000	[thread overview]
Message-ID: <fca0b32cea2f41319482192514998178@huawei.com> (raw)
In-Reply-To: 20210222160143.GJ2643399@ziepe.ca

On 2021/2/23 0:02, Jason Gunthorpe wrote:
> On Sat, Feb 20, 2021 at 08:40:02AM +0000, liweihang wrote:
>> On 2021/2/10 3:54, Jason Gunthorpe wrote:
>>> On Sun, Feb 07, 2021 at 11:12:49AM +0800, Weihang Li wrote:
>>>> The HIP09 introduces the DCA(Dynamic Context Attachment) feature which
>>>> supports many RC QPs to share the WQE buffer in a memory pool. If a QP
>>>> enables DCA feature, the WQE's buffer will not be allocated when creating
>>>> but when the users start to post WRs. This will reduce the memory
>>>> consumption when there are too many QPs are inactive.
>>>> One a WQE buffer is allocated it still acts as a normal WQE ring
>>> buffer? So this DCA logic is to remap the send queue buffer based on
>>> demand for SQEs? How does it interact with the normal max send queue
>>> entries reported?
>>>
>>
>> Not exactly. If DCA is enabled, we first allocate a memory pool with a
>> default size when opening device. Each time we trying to post WR(s) to a
>> QP, the driver will check if current QP has WQE buffer.
>>
>> If not, the driver will check whether there is enough free memory in the
>> DCA memory pool. If there is, the QP will get WQE buffer from the
>> pool,
> 
> Does that mean the QP can have a non-contiguous list of buffers? Ie it
> isn't just a linear ring of memory?
> 
> Jason
> 

Yes, when using multilevel addressing, the virtual address of QP's buffers
may be non-contiguous to avoid memory fragmentation.

Weihang

  reply	other threads:[~2021-02-23  8:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07  3:12 [PATCH RFC rdma-core 0/5] libhns: Add support for Dynamic Context Attachment Weihang Li
2021-02-07  3:12 ` [PATCH RFC rdma-core 1/5] Update kernel headers Weihang Li
2021-02-07  3:12 ` [PATCH RFC rdma-core 2/5] libhns: Introduce DCA for RC QP Weihang Li
2021-02-09 19:44   ` Jason Gunthorpe
2021-02-20  6:12     ` liweihang
2021-02-07  3:12 ` [PATCH RFC rdma-core 3/5] libhns: Add support for shrinking DCA memory pool Weihang Li
2021-02-07  3:12 ` [PATCH RFC rdma-core 4/5] libhns: Add support for attaching QP's WQE buffer Weihang Li
2021-02-07  3:12 ` [PATCH RFC rdma-core 5/5] libhns: Add support for configuring DCA Weihang Li
2021-02-09 19:38 ` [PATCH RFC rdma-core 0/5] libhns: Add support for Dynamic Context Attachment Jason Gunthorpe
2021-02-20  9:47   ` liweihang
2021-02-09 19:53 ` Jason Gunthorpe
2021-02-20  8:40   ` liweihang
2021-02-22 16:01     ` Jason Gunthorpe
2021-02-23  8:07       ` liweihang [this message]
2021-02-24  9:48   ` liweihang
2021-02-24 18:55     ` Jason Gunthorpe

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=fca0b32cea2f41319482192514998178@huawei.com \
    --to=liweihang@huawei.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linuxarm@openeuler.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.