[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tencent_BC7A3D486E923DFD8C99DFCFEA79B82A8205@qq.com>
Date: Mon, 2 Oct 2023 23:12:13 +0800
From: Wen Yang <wenyang.linux@...mail.com>
To: Jens Axboe <axboe@...nel.dk>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>
Cc: Christoph Hellwig <hch@....de>, Dylan Yudaken <dylany@...com>,
David Woodhouse <dwmw@...zon.co.uk>,
Matthew Wilcox <willy@...radead.org>,
Eric Biggers <ebiggers@...gle.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] eventfd: move 'eventfd-count' printing out of spinlock
On 2023/9/27 15:32, Jens Axboe wrote:
> On 9/26/23 8:05 AM,wenyang.linux@...mail.com wrote:
>> From: Wen Yang<wenyang.linux@...mail.com>
>>
>> It is better to print debug messages outside of the wqh.lock
>> spinlock where possible.
> Does it really matter for fdinfo? Your commit message is a bit
> light, so I'm having to guess whether this is fixing a real issue
> for you, or if it's just a drive-by observation.
>
Thanks for your comments.
There is a business running on our machine that frequently calls
eventfd_write().
We will resend the V2 and provide a detailed explanation.
--
Best wishes,
Wen
Powered by blists - more mailing lists