From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Shares with strange ACL settings
Date: Mon, 17 Aug 2015 14:53:00 -0000 [thread overview]
Message-ID: <20150817145339.GG17917@calimero.vinschen.de> (raw)
In-Reply-To: <loom.20150817T150702-368@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]
On Aug 17 13:12, Achim Gratz wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
>
> > No worries and thank you. I just don't quite understand the stuff
> > returned by 8000001e and what I see above.
>
> Different architectures, so these are not expected to match.
Sure, I wasn't expecting that. I referred to the cpuid output you
provided and the matching info from your OP starting this subthread.
> > Do I understand this
> > correctly that a single CPU has 2 NUMA nodes? Does that mean a single
> > HW socket consists of two independent 6 core CPUs?
>
> In the case above, yes. MagnyCours is two Istanbul dies in one package.
>
> > Well, anyway, I just got remote access to a 2 socket systems with
> > Opteron 6386SE CPUs. It's installing rhel7 right now so I might get
> > another clue from there.
>
> Yes, that should help. That's again two dies per package, each with 8
> processors paired inside 4 modules. Each of the two die should be more or
> less identical to the 6328, save for clock frequency.
Indeed, looking into the output provided by the 6328SE and some 12 core
MagnyCours CPU I forgot the number of, was helpful. I *think* I fixed
the cpuinfo now for new AMDs which provide 0x800001e topology info.
Please give the latest snapshot from https://cygwin.com/snapshots/
a try.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-17 14:53 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 8:42 Achim Gratz
2015-08-11 17:20 ` Andrey Repin
2015-08-11 17:29 ` Achim Gratz
2015-08-12 15:26 ` Corinna Vinschen
2015-08-12 15:50 ` Achim Gratz
2015-08-12 15:58 ` Corinna Vinschen
2015-08-12 18:09 ` Achim Gratz
2015-08-12 18:32 ` Corinna Vinschen
2015-08-12 21:03 ` Achim Gratz
2015-08-13 16:33 ` Corinna Vinschen
2015-08-13 17:48 ` Achim Gratz
2015-08-13 17:53 ` Corinna Vinschen
2015-08-14 8:30 ` Corinna Vinschen
2015-08-14 10:56 ` Achim Gratz
2015-08-14 13:45 ` Corinna Vinschen
2015-08-14 18:25 ` Achim Gratz
2015-08-14 18:43 ` Corinna Vinschen
2015-08-17 8:20 ` Corinna Vinschen
2015-08-15 15:11 ` Achim Gratz
2015-08-15 18:31 ` Corinna Vinschen
2015-08-15 19:04 ` Achim Gratz
2015-08-17 8:28 ` Achim Gratz
2015-08-17 9:03 ` Corinna Vinschen
2015-08-17 9:12 ` Achim Gratz
2015-08-17 10:45 ` Corinna Vinschen
2015-08-17 10:51 ` Achim Gratz
2015-08-17 11:03 ` Corinna Vinschen
2015-08-17 11:09 ` Achim Gratz
2015-08-17 11:31 ` Corinna Vinschen
2015-08-17 11:39 ` Corinna Vinschen
2015-08-17 11:43 ` Achim Gratz
2015-08-17 12:42 ` Achim Gratz
2015-08-17 12:56 ` Corinna Vinschen
2015-08-17 13:12 ` Achim Gratz
2015-08-17 14:53 ` Corinna Vinschen [this message]
2015-08-17 15:47 ` Achim Gratz
2015-08-17 16:11 ` Corinna Vinschen
2015-08-15 15:41 ` Marco Atzeri
2015-08-15 18:32 ` Corinna Vinschen
2015-08-13 17:56 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150817145339.GG17917@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).