linux-kernel - Re: [RFC] [PATCH 1/2] binary stream format for /proc/stat

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]

Message-ID: <CABEgKgo7DUZj9NAdHoEiSDv0_kTNFFjD04T6AKc19WavmGiNog@mail.gmail.com>
Date:	Sun, 1 Apr 2012 06:23:31 +0900
From:	Hiroyuki Kamezawa <kamezawa.hiroyuki@...il.com>
To:	Jan Engelhardt <jengelh@...ozas.de>
Cc:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Alexey Dobriyan <adobriyan@...il.com>,
	Ulrich Drepper <drepper@...il.com>
Subject: Re: [RFC] [PATCH 1/2] binary stream format for /proc/stat

2012年3月31日23:42 Jan Engelhardt <jengelh@...ozas.de>:
> On Tuesday 2012-03-27 10:53, KAMEZAWA Hiroyuki wrote:
>
>>Provides another format of /proc/stat for showing data in binary and
>>compress sequence of Zeros to some extent.
>>
>>Any other idea of formats ?
>
> Rather than adding more obscure formats and fields to /proc(/N)/stat, we
> should pursue descriptive lines like in /proc/N/status.
> Or, if so desired, sysfs-style splitted attributes where the filename
> takes on the description.

Yes, I like format like /proc/N/status , /proc/meminfo...which is
readable to me.
But when I wrote this patch, I didn't want to break current format.

My concern on sysfs-style one data per a file is that it will add many
open/close and making top/ps/sar slow.

Thanks,
-Kame
--
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/