linux-kernel - Re: [PATCH 0/3] x86: add cpus

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: <36ca99e90804100914n4b08cc9di9a6ab8b936f25644@mail.gmail.com>
Date:	Thu, 10 Apr 2008 18:14:55 +0200
From:	"Bert Wesarg" <bert.wesarg@...glemail.com>
To:	"Paul Jackson" <pj@....com>
Cc:	travis@....com, mingo@...e.hu, tglx@...utronix.de, hpa@...or.com,
	akpm@...ux-foundation.org, gregkh@...e.de,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] x86: add cpus_scnprintf function v3

On Thu, Apr 10, 2008 at 2:10 PM, Paul Jackson <pj@....com> wrote:
> Bert wrote:
>  > Btw, I think you can now push for a deprecation of the 'old' mask
>  > attributes, with the justification you have given above. The other
>  > possibility is to change sysfs to provide bigger attribute buffers
>  > (CCed Greg for this).
>
>  On the other hand, and my main point of this message, I can't
>  see deprecating the mask format files on account of this sort
>  of analysis.
>
My statement from above doesn't reflect my opinion. I'm still in
flavor with the mask output. And from this discussion, I found a new
point for the mask output: its bounded ;-)

I just wanted to note, that these new list attributes would be the
only way to 'change' the api, ie. introduce a new api and deprecate
the old one, and not change the format of the present api.

Unfortunately, to support the mask attributes beyond 4k cpus, sysfs
has to support greater attribute buffers.

Bert
--
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/