All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dust Li <dust.li@linux.alibaba.com>
To: Halil Pasic <pasic@linux.ibm.com>, Paolo Abeni <pabeni@redhat.com>
Cc: Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
	"D. Wythe" <alibuda@linux.alibaba.com>,
	Sidraya Jayagond <sidraya@linux.ibm.com>,
	Wenjia Zhang <wenjia@linux.ibm.com>,
	Mahanta Jambigi <mjambigi@linux.ibm.com>,
	Tony Lu <tonylu@linux.alibaba.com>,
	Wen Gu <guwen@linux.alibaba.com>,
	netdev@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-s390@vger.kernel.org
Subject: Re: [PATCH net-next v3 1/2] net/smc: make wr buffer count configurable
Date: Sun, 28 Sep 2025 10:02:43 +0800	[thread overview]
Message-ID: <aNiXQ_UfG9k-f9-n@linux.alibaba.com> (raw)
In-Reply-To: <20250928005515.61a57542.pasic@linux.ibm.com>

On 2025-09-28 00:55:15, Halil Pasic wrote:
>On Thu, 25 Sep 2025 13:25:40 +0200
>Halil Pasic <pasic@linux.ibm.com> wrote:
>
>> > [...]  
>> > > @@ -683,6 +678,8 @@ int smc_ib_create_queue_pair(struct smc_link *lnk)
>> > >  	};
>> > >  	int rc;
>> > >  
>> > > +	qp_attr.cap.max_send_wr = 3 * lnk->lgr->max_send_wr;
>> > > +	qp_attr.cap.max_recv_wr = lnk->lgr->max_recv_wr;    
>> > 
>> > Possibly:
>> > 
>> > 	cap = max(3 * lnk->lgr->max_send_wr, lnk->lgr->max_recv_wr);
>> > 	qp_attr.cap.max_send_wr = cap;
>> > 	qp_attr.cap.max_recv_wr = cap
>> > 
>> > to avoid assumption on `max_send_wr`, `max_recv_wr` relative values.  
>> 
>> Can you explain a little more. I'm happy to do the change, but I would
>> prefer to understand why is keeping qp_attr.cap.max_send_wr ==
>> qp_attr.cap.max_recv_wr better? But if you tell: "Just trust me!" I will.
>
>Due to a little accident we ended up having a private conversation
>on this, which I'm going to sum up quickly.
>
>Paolo stated that he has no strong preference and that I should at
>least add a comment, which I will do for v4. 
>
>Unfortunately I don't quite understand why qp_attr.cap.max_send_wr is 3
>times the number of send WR buffers we allocate. My understanding
>is that qp_attr.cap.max_send_wr is about the number of send WQEs.

We have at most 2 RDMA Write for 1 RDMA send. So 3 times is necessary.
That is explained in the original comments. Maybe it's better to keep it.

```
.cap = {
                /* include unsolicited rdma_writes as well,
                 * there are max. 2 RDMA_WRITE per 1 WR_SEND
                 */
        .max_send_wr = SMC_WR_BUF_CNT * 3,
        .max_recv_wr = SMC_WR_BUF_CNT * 3,
        .max_send_sge = SMC_IB_MAX_SEND_SGE,
        .max_recv_sge = lnk->wr_rx_sge_cnt,
        .max_inline_data = 0,
},
```

>I assume that qp_attr.cap.max_send_wr == qp_attr.cap.max_recv_wr
>is not something we would want to preserve.

IIUC, RDMA Write won't consume any RX wqe on the receive side, so I think
the .max_recv_wr can be SMC_WR_BUF_CNT if we don't use RDMA_WRITE_IMM.


Best regards,
Dust

  reply	other threads:[~2025-09-28  2:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-21 21:44 [PATCH net-next v3 0/2] net/smc: make wr buffer count configurable Halil Pasic
2025-09-21 21:44 ` [PATCH net-next v3 1/2] " Halil Pasic
2025-09-24 17:27   ` Sidraya Jayagond
2025-09-25  9:27   ` Paolo Abeni
2025-09-25 11:25     ` Halil Pasic
2025-09-27 22:55       ` Halil Pasic
2025-09-28  2:02         ` Dust Li [this message]
2025-09-28  2:12           ` Dust Li
2025-09-28  8:39           ` Halil Pasic
2025-09-28 11:42             ` Dust Li
2025-09-28 18:32               ` Halil Pasic
2025-09-26  2:44   ` Guangguan Wang
2025-09-26 10:12     ` Halil Pasic
2025-09-26 10:30       ` Halil Pasic
2025-09-28  3:05         ` Guangguan Wang
2025-09-21 21:44 ` [PATCH net-next v3 2/2] net/smc: handle -ENOMEM from smc_wr_alloc_link_mem gracefully Halil Pasic
2025-09-24 17:28   ` Sidraya Jayagond
2025-09-25  9:40   ` Paolo Abeni
2025-09-25 15:05     ` Halil Pasic
2025-09-25 15:41       ` Paolo Abeni
2025-09-25 21:46         ` Halil Pasic

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=aNiXQ_UfG9k-f9-n@linux.alibaba.com \
    --to=dust.li@linux.alibaba.com \
    --cc=alibuda@linux.alibaba.com \
    --cc=guwen@linux.alibaba.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mjambigi@linux.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pasic@linux.ibm.com \
    --cc=sidraya@linux.ibm.com \
    --cc=tonylu@linux.alibaba.com \
    --cc=wenjia@linux.ibm.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 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.