Comments on: Never too many cores https://www.dragonflydigest.com/2018/02/26/never-too-many-cores/ A running description of activity related to DragonFly BSD. Wed, 28 Feb 2018 06:41:14 +0000 hourly 1 https://wordpress.org/?v=7.0 By: Anonymous https://www.dragonflydigest.com/2018/02/26/never-too-many-cores/comment-page-1/#comment-487233 Wed, 28 Feb 2018 06:41:14 +0000 https://www.dragonflydigest.com/?p=20940#comment-487233 I wonder how htop looks like on this system!

]]> By: T https://www.dragonflydigest.com/2018/02/26/never-too-many-cores/comment-page-1/#comment-487232 Tue, 27 Feb 2018 19:55:10 +0000 https://www.dragonflydigest.com/?p=20940#comment-487232 Wow. Would love to read an article on running Dfly on this beast.

@zrj, in case you read this comment. Please blog about this beast. Would be fascinating read.

]]> By: Anonymous https://www.dragonflydigest.com/2018/02/26/never-too-many-cores/comment-page-1/#comment-487231 Tue, 27 Feb 2018 19:01:53 +0000 https://www.dragonflydigest.com/?p=20940#comment-487231 How long does a buildworld / buildkernel take on this beast?

]]> By: Justin Sherrill https://www.dragonflydigest.com/2018/02/26/never-too-many-cores/comment-page-1/#comment-487230 Tue, 27 Feb 2018 14:19:38 +0000 https://www.dragonflydigest.com/?p=20940#comment-487230 Yes – a much larger system. Ask zrj on #dragonflybsd as he is the one running it; it sounds fascinating.

]]> By: T https://www.dragonflydigest.com/2018/02/26/never-too-many-cores/comment-page-1/#comment-487229 Tue, 27 Feb 2018 14:16:36 +0000 https://www.dragonflydigest.com/?p=20940#comment-487229 Justin

When you say:

“
T – a virtual computer pulling from a huge inventory.
”

What do you mean by “huge inventory”?

I didn’t even know there were x86 systems that had 11+ sockets.

Is this some type of multi-node cluster that is appearing as a single server?

]]> By: Justin Sherrill https://www.dragonflydigest.com/2018/02/26/never-too-many-cores/comment-page-1/#comment-487217 Tue, 27 Feb 2018 04:36:37 +0000 https://www.dragonflydigest.com/?p=20940#comment-487217 Eric – I think it’s a timing issue. That’s an automatic note that happens when one process is trying to unmount a device while another device is still using it. There’s no harm – it just keeps retrying until the device isn’t being used any more.

I’m not the authoritative answer, though – a good question for IRC.

T – a virtual computer pulling from a huge inventory.

]]> By: T https://www.dragonflydigest.com/2018/02/26/never-too-many-cores/comment-page-1/#comment-487214 Mon, 26 Feb 2018 20:16:19 +0000 https://www.dragonflydigest.com/?p=20940#comment-487214 What piece of hardware has 11 sockets?

]]> By: Eric Olson https://www.dragonflydigest.com/2018/02/26/never-too-many-cores/comment-page-1/#comment-487213 Mon, 26 Feb 2018 17:40:35 +0000 https://www.dragonflydigest.com/?p=20940#comment-487213 What do you think of the message

malloc_uninit: 120 bytes of ‘HAMMER2-chains’ still allocated on cpu 110
kthread 0xfffffae0e28dd300 syncer3 has exited
vflush: Warning, cannot destroy busy device vnode
unmount of filesystem mounted from devfs failed (BUSY)

associated with the system shutdown at the end?

]]>