public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Qiang <liqiang64@huawei.com>
To: <dust.li@linux.alibaba.com>, <wenjia@linux.ibm.com>,
	<jaka@linux.ibm.com>, <alibuda@linux.alibaba.com>,
	<tonylu@linux.alibaba.com>, <guwen@linux.alibaba.com>
Cc: <linux-s390@vger.kernel.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <luanjianhai@huawei.com>,
	<zhangxuzhou4@huawei.com>, <dengguangxing@huawei.com>,
	<gaochao24@huawei.com>
Subject: Re: [PATCH] net/smc: Optimize the search method of reused buf_desc
Date: Fri, 1 Nov 2024 16:27:23 +0800	[thread overview]
Message-ID: <6d5bfce0-b01d-b46b-3a9f-5291455f3022@huawei.com> (raw)
In-Reply-To: <20241101065016.GF101007@linux.alibaba.com>



在 2024/11/1 14:50, Dust Li 写道:
> On 2024-10-29 14:54:15, liqiang wrote:
>> We create a lock-less link list for the currently 
>> idle reusable smc_buf_desc.
>>
>> When the 'used' filed mark to 0, it is added to 
>> the lock-less linked list. 
>>
>> When a new connection is established, a suitable 
>> element is obtained directly, which eliminates the 
>> need for traversal and search, and does not require 
>> locking resource.
>>
>> A lock-free linked list is a linked list that uses 
>> atomic operations to optimize the producer-consumer model.
> 
> Do you see any performance issues without this lock-less linked list ?
> Under what test case ? Any performance numbers would be welcome
> 

I optimized it through review. I re-sent this patch based on the
net-next repo. It contains some of my own test data. Please check it. :-)

> Best regards,
> Dust
> 
> .
> 

-- 
Cheers,
Li Qiang

  reply	other threads:[~2024-11-01  8:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29  6:54 [PATCH] net/smc: Optimize the search method of reused buf_desc liqiang
2024-11-01  2:06 ` Jakub Kicinski
2024-11-01  3:11   ` Li Qiang
2024-11-01  6:50 ` Dust Li
2024-11-01  8:27   ` Li Qiang [this message]
2024-11-04  1:41 ` D. Wythe
2024-11-04  7:34   ` Li Qiang

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=6d5bfce0-b01d-b46b-3a9f-5291455f3022@huawei.com \
    --to=liqiang64@huawei.com \
    --cc=alibuda@linux.alibaba.com \
    --cc=dengguangxing@huawei.com \
    --cc=dust.li@linux.alibaba.com \
    --cc=gaochao24@huawei.com \
    --cc=guwen@linux.alibaba.com \
    --cc=jaka@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=luanjianhai@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=tonylu@linux.alibaba.com \
    --cc=wenjia@linux.ibm.com \
    --cc=zhangxuzhou4@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox