Your message dated Wed, 14 May 2025 20:56:42 +0200 with message-id <20250514185642.s4rcew6mbfcty...@shell.thinkmo.de> and subject line not in debian has caused the Debian Bug report #960935, regarding linux: please enable CONFIG_NUMA on sparc64 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 960935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: linux Severity: wishlist Hi! While discussing porting one of my packages to sparc64 (I wanted to run its tests, requiring the NUMA API, at least on a single machine) I was told that a lot of sparc64 machines in the wild have multiple sockets. Sparc architecture in general tends to have a lot of slow CPUs, using many-way SMT and NUMA nodes. As cross-socket accesses are in general a same-week service, it would be a good idea to enable this API so programs can be aware of NUMA setups. Thus: could you please set CONFIG_NUMA=y on linux-image-sparc64-smp? Meow!
--- End Message ---
--- Begin Message ---sparc64 is not in bullseye: linux-libc-dev | 5.10.223-1 | oldstable | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x Bastian -- ... The prejudices people feel about each other disappear when they get to know each other. -- Kirk, "Elaan of Troyius", stardate 4372.5
--- End Message ---
