All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai <KaiShen@linux.alibaba.com>
To: Wenjia Zhang <wenjia@linux.ibm.com>,
	Guangguan Wang <guangguan.wang@linux.alibaba.com>,
	kgraul@linux.ibm.com, jaka@linux.ibm.com
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
	linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next v2] net/smc: Use percpu ref for wr tx reference
Date: Wed, 1 Mar 2023 09:44:41 +0800	[thread overview]
Message-ID: <a1516a5e-4d8b-f00c-cecd-e1b2f124fdcd@linux.alibaba.com> (raw)
In-Reply-To: <d1b06606-f01c-918e-0921-5d6c697f9c89@linux.ibm.com>



On 2023/2/28 8:52 下午, Wenjia Zhang wrote:
> 
> 
> On 28.02.23 13:15, Guangguan Wang wrote:
>>
>> On 2023/2/28 19:34, Kai wrote:
>>>
>>>
>>> On 2023/2/28 6:55 下午, Wenjia Zhang wrote:
>>>
>>>> @Kai, the performance improvement seems not so giant, but the method 
>>>> looks good, indeed. However, to keep the consistency of the code, 
>>>> I'm wondering why you only use the perf_ref for wr_tx_wait, but not 
>>>> for wr_reg_refcnt?
>>> Didn't check the similar refcnt, my bad.
>>> On the other hand, Our work is inspired by performance analysis, it 
>>> seems wr_reg_refcnt is not on the IO path. It may not contribute to 
>>> performance improvement.
>>> And inspired by your comment, it seems we can also make the refcnt 
>>> cdc_pend_tx_wr a perfcpu one. I will look into this.
>>>
>>> Thanks
>>
>> cdc_pend_tx_wr needs to be zero value tested every time it decreases 
>> in smc_cdc_tx_handler.
>> I don't think this is the right scenario for percpu_ref.
> 
> I agree, that's why I didn't mention it;)
> 
> But could you please check about wr_reg_refcnt? Because we do need to 
> find the right balance between the code consistency and improvement
Will do

      reply	other threads:[~2023-03-01  1:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 12:16 [PATCH net-next v2] net/smc: Use percpu ref for wr tx reference Kai
2023-02-28 10:55 ` Wenjia Zhang
2023-02-28 11:34   ` Kai
2023-02-28 12:15     ` Guangguan Wang
2023-02-28 12:20       ` Kai
2023-02-28 12:52       ` Wenjia Zhang
2023-03-01  1:44         ` Kai [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=a1516a5e-4d8b-f00c-cecd-e1b2f124fdcd@linux.alibaba.com \
    --to=kaishen@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=guangguan.wang@linux.alibaba.com \
    --cc=jaka@linux.ibm.com \
    --cc=kgraul@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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.