X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=TiZnN
	MhGUuPqQlNXrORVV8wgmP8zyKE6bsK0nDprT7nZ8TAgTb7RHARVCkIbyHIrEB2KD
	3hme4cXg3I27a6sbIzR4fdTQ0u8C5KLaRVLbB2MdT7aa/OixIKHgUjiY7oBfjH34
	OHNCHw/KLPBN3bZP+uJBTN5tKxZmQT6suLLz54=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; s=default; bh=CY3p8z5NF9R
	i1wg0JbTs+r3w2eo=; b=QVRYFMPdBpQAH0naOfmfTGFzmArghkRSdOypWKTGpO1
	6cU+eo6LvSCiuLRaCGHAUQ7E3dxNHrEUSdvv/vKrJf3/xpcHXtN+IYLW8Tr2VxxP
	Y9QsQ+r6JrI+JGOIhHtV0sIYEtlKn+Eiuey6IIq0+Z+51P3WWAVA/hqy8BHgrjfQ
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-in-16.arcor-online.net
X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-11.arcor-online.net 3mtrfR0ln4z31mX
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Shares with strange ACL settings
References: <20150812155817.GN13029@calimero.vinschen.de>	<878u9g9y6b.fsf@Rainer.invalid>	<20150812183220.GO13029@calimero.vinschen.de>	<87vbck8h92.fsf@Rainer.invalid>	<20150813163302.GB28349@calimero.vinschen.de>	<20150813175302.GD28349@calimero.vinschen.de>	<20150814082959.GE28349@calimero.vinschen.de>	<loom.20150814T125223-728@post.gmane.org>	<20150814134552.GG28349@calimero.vinschen.de>	<87bne8d1tm.fsf@Rainer.invalid>	<20150815183126.GT28349@calimero.vinschen.de>
Date: Sat, 15 Aug 2015 21:04:27 +0200
In-Reply-To: <20150815183126.GT28349@calimero.vinschen.de> (Corinna Vinschen's	message of "Sat, 15 Aug 2015 20:31:26 +0200")
Message-ID: <87vbcgbcg4.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Corinna Vinschen writes:
>> I've also tried to find out why the L3 cache is not reported for AMD in
>> cpuinfo.  It seems the reason is that it is logically part of the
>> northbridge system, even if it is on-die and gets reported via CPUID.
>
> Ok, interesting.  Still strange, isn't it?

In any case, it's not due to an inability to get at the cache sizes.
The code that fills those in has the sizes for all levels, but the cache
size structure that gets used in /proc/cpuinfo is filled from L2 on AMD
and L3 on Intel.  If you need the full information on Linux you'd go to
/sys/devices/system/cpu or use one of the more specialized programs that
give you topology information anyway.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

