All of lore.kernel.org
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.ibm.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
	"D. Wythe" <alibuda@linux.alibaba.com>,
	Dust Li <dust.li@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, Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [PATCH net-next v3 1/2] net/smc: make wr buffer count configurable
Date: Thu, 25 Sep 2025 13:25:40 +0200	[thread overview]
Message-ID: <20250925132540.74091295.pasic@linux.ibm.com> (raw)
In-Reply-To: <7cc2df09-0230-40cb-ad4f-656b0d1d785b@redhat.com>

On Thu, 25 Sep 2025 11:27:38 +0200
Paolo Abeni <pabeni@redhat.com> wrote:
[..]
> > +smcr_max_recv_wr - INTEGER
> > +	So called work request buffers are SMCR link (and RDMA queue pair) level
> > +	resources necessary for performing RDMA operations. Since up to 255
> > +	connections can share a link group and thus also a link and the number
> > +	of the work request buffers is decided when the link is allocated,
> > +	depending on the workload it can a bottleneck in a sense that threads  
> 
> same                               here^^

Sorry about those! Will fix for v4.

> 
> [...]
> > @@ -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.

[..]

> >  
> > diff --git a/net/smc/smc_wr.c b/net/smc/smc_wr.c
> > index b04a21b8c511..f5b2772414fd 100644
> > --- a/net/smc/smc_wr.c
> > +++ b/net/smc/smc_wr.c
> > @@ -34,6 +34,7 @@
> >  #define SMC_WR_MAX_POLL_CQE 10	/* max. # of compl. queue elements in 1 poll */
> >  
> >  #define SMC_WR_RX_HASH_BITS 4
> > +  
> 
> Please avoid unrelated whitespace only changes.

Will fix  for v4. Really sorry!

Regards,
Halil

  reply	other threads:[~2025-09-25 11:25 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 [this message]
2025-09-27 22:55       ` Halil Pasic
2025-09-28  2:02         ` Dust Li
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=20250925132540.74091295.pasic@linux.ibm.com \
    --to=pasic@linux.ibm.com \
    --cc=alibuda@linux.alibaba.com \
    --cc=dust.li@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=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.