lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tencent_6A42A1EE91831C3D5B94CECC5F8B12C3B107@qq.com>
Date: Mon, 7 Apr 2025 09:25:53 +0800
From: Yaxiong Tian <iambestgod@...com>
To: Christoph Hellwig <hch@....de>
Cc: kbusch@...nel.org, axboe@...nel.dk, sagi@...mberg.me,
 chaitanyak@...dia.com, linux-nvme@...ts.infradead.org,
 linux-kernel@...r.kernel.org, Yaxiong Tian <tianyaxiong@...inos.cn>,
 alexey.bogoslavsky@....com
Subject: Re: [PATCH v3 0/3] nvme: Add sysfs interface for APST configuration
 management



在 2025/4/4 16:29, Christoph Hellwig 写道:
> On Thu, Apr 03, 2025 at 03:05:37PM +0800, Yaxiong Tian wrote:
>> These two patches don't fundamentally change the APST configuration policy,
>> but rather enable users to configure various APST parameters in real-time
>> across different devices. As mentioned in commit <ebd8a93aa4f5> ("nvme:
>> extend and modify the APST configuration algorithm"):
> 
> And who are those users?  What tools do they use.  What settings do they
> set and why?
The three issues you mentioned were actually partially addressed in the 
previous email, or at least touched upon.

In any case, I agree with applying a universal setting for APST, as I 
don’t have a good tool to handle this either Now.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ