Comments on: DragonFly 5.4 released!

By: dfuser

dfuser — Wed, 05 Dec 2018 13:32:22 +0000

justin makes the announcement and everyone on the net starts spreading the new stuff of 5.4 as written on the release page and then matt passes a few times on the release page making it geek techy like always.. will robots update they news bodies? don’t think so..

but hey, who cares, people stick to dfly and people are attracted to it because they really read from the dfly domain, from wiki AND git!

my kernel is not generic, but I think I can manage, is so simple. I kinda wanted a justin -vvv on the update to 5.4 cases.

By: Justin Sherrill

Justin Sherrill — Wed, 05 Dec 2018 05:28:43 +0000

When everyone says “hey let’s call it 6.0”. Barring surprises, I would expect we’d go to 6.0 instead of 5.10 just cause the x.10 number causes a bunch of minor issues around numbering and version reporting, as we all found out around 4.10.

By: Anonymous

Anonymous — Wed, 05 Dec 2018 04:52:02 +0000

Justin

So if releases are calendar driven vs feature driven … then what defines when the next release will be call “6.0” vs “5.6”?

By: Justin Sherrill

Justin Sherrill — Tue, 04 Dec 2018 17:45:46 +0000

Anonymous – releases are calendar-driven, not feature-driven.

By: Anonymous

Anonymous — Tue, 04 Dec 2018 13:59:18 +0000

Since Hammer2 was the big ticket item for the v5.0 release – what’s the big ticket item people are working on for the v6.0 release?

By: Anonymous

Anonymous — Tue, 04 Dec 2018 08:49:32 +0000

Thanks to the whole team for its work on DragonFly, upgrade from 5.2.2 was flawless as always !

By: Justin Sherrill

Justin Sherrill — Tue, 04 Dec 2018 01:21:09 +0000

Don – why did you think that? I’ve been linking to AMD-related DragonFly stuff for years.

By: Don Park

Don Park — Mon, 03 Dec 2018 23:49:18 +0000

I’m a bit confused. I thought dragonfly was targeted to intel 64bit features. to my knowledge there is no intel NUMA cpu.

By: Anonymous

Anonymous — Mon, 03 Dec 2018 19:16:12 +0000

Justin

What was super helpful. Thanks

By: Justin Sherrill

Justin Sherrill — Mon, 03 Dec 2018 17:50:17 +0000

NUMA means the system has different memory types of varying speeds accessible to CPUs – on-die, RAM, etc.

Asymmetric NUMA means every CPU has access to different memory types, but not all the CPUs have access to the same types. i.e. you can’t count on the particular CPU you are executing on to be connected to a directly-attached memory controller, cause there’s 4 CPUs but only 2 controllers in the system – for instance.

By: Anonymous

Anonymous — Mon, 03 Dec 2018 17:40:12 +0000

I understand what NUMA is. What’s “asymmetric”

By: Justin Sherrill

Justin Sherrill — Mon, 03 Dec 2018 16:51:14 +0000

You mean dports, not pkgsrc, correct?

I don’t see gluster as a built package, which could mean a number of things. I’ve never tried building it; never used it.

By: josias

josias — Mon, 03 Dec 2018 15:07:54 +0000

Hi.
Have some effort to build glusterFS in pkgsrc ?.
I not find any info about this on google and works on FreeBSD.
I think glusterfs + hammerfs 2 would be very nice to dcs.
good work on dragonfly.

By: Justin Sherrill

Justin Sherrill — Mon, 03 Dec 2018 14:52:06 +0000

https://en.wikipedia.org/wiki/Non-uniform_memory_access

I’ll link it in the article, too.

By: Anonymous

Anonymous — Mon, 03 Dec 2018 14:50:44 +0000

What’s the ELI5 version of “asymmetric NUMA”.

I’ve googled some but I must be too much of a noob to understand the articles I found.