Phil Carns

A short term workaround would be to crank up that #define if we don't have chunking capability yet :) BMI should technically work with a larger limit, and will actually...

My 2c: I think there might be a use for something like tw_event_new_large(), but I think an easier problem to tackle is that even if the pre-allocated event buffers have...

Rather than document the flags explicitly, it would be better to document the use of ross-config for this stuff. That way as long as ross-config is kept up to date...

Random comment: I can think of one possible workaround. When you issue the timeout event, store (in your state struct) a variable indicating the target timestamp value when that timeout...

FYI, Mercury 2.x is intended to at least print a friendly error message in the case where it detected that a) the platform supports CMA but b) due to security/permission...

I'm not familiar enough with these mechanism to comment on @bfaccini 's proposal, but I am interested in this topic. FWIW we often use external libraries (communication libraries in particular,...

Hi @halimamer, we actually need to replace both the pool and scheduler for the main xstream. Can we do that with the ABT_pool_add_sched() function, or will that just replace the...

The Unify team is aware of the build problem and looking at how to best handle it. We can re-kick the CI action once we get an all clear from...

@jolivier23 just curious, does the memory consumption change if you set the ABT_MEM_MAX_NUM_STACKS environment variable? FWIW the default value of this parameter is 65536, but in Margo we set it...

> @carns in looking at the code, it looks like the max is 1024 now > > ``` > #define ABTD_MEM_MAX_NUM_STACKS 1024 > ... > const uint32_t default_mem_max_stacks = >...