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] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 30 Nov 2007 23:31:13 -0500
From:	Mark Lord <lkml@....ca>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
	Andrew Morton <akpm@...ux-foundation.org>, abelay@...ell.com,
	lenb@...nel.org, rjw@...k.pl, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org
Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

Mark Lord wrote:
> Arjan van de Ven wrote:
>> On Fri, 30 Nov 2007 22:44:25 -0500
>> Mark Lord <lkml@....ca> wrote:
>>>> all you need to do in your kernel module is call
...
>> set_acceptable_latency("mark", 5);
>>
>> and to remove the constraint again you just do
>>
>> remove_acceptable_latency("mark");
..
>>> Then why not have a sysfs entry for scripts to write tsoro
>>> to trigger the exact same end result?  :)
>>
>> that's what is in current -mm pretty much
>> well not sysfs, but it goes via a file descriptor
>> (so that if the process that sets the contraint dies, the latency
>> requirement can be given up automatically)
> ...
> 
> But doesn't that approach also make it nearly impossible to script ????
...

Okay, I have a working trivial kernel module that I can load/unload
to tweak this.  But a simple sysfs attribute would be *so much* better
as a permanent kernel feature.

Binary interfaces (fd) are fine for some uses, but not nice for scripts.

Cheers
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ