On 9/27/2018 12:48 PM, Dan Williams wrote:
On Thu, Sep 27, 2018 at 8:24 AM Alexander Duyck
wrote:
[..]
- * Returns an async_cookie_t that may be used for checkpointing later.
- * @domain may be used in the async_synchronize_*_domain() functions to
- * wait within a certain synchronization
On Thu, Sep 27, 2018 at 8:24 AM Alexander Duyck
wrote:
[..]
> >> - * Returns an async_cookie_t that may be used for checkpointing later.
> >> - * @domain may be used in the async_synchronize_*_domain() functions to
> >> - * wait within a certain synchronization domain rather than globally. A
>
On 9/26/2018 5:31 PM, Dan Williams wrote:
On Wed, Sep 26, 2018 at 2:51 PM Alexander Duyck
wrote:
This patch introduces four new variants of the async_schedule_ functions
that allow scheduling on a specific NUMA node.
The first two functions are async_schedule_near and
On Wed, Sep 26, 2018 at 2:51 PM Alexander Duyck
wrote:
>
> This patch introduces four new variants of the async_schedule_ functions
> that allow scheduling on a specific NUMA node.
>
> The first two functions are async_schedule_near and
> async_schedule_near_domain which end up mapping to
This patch introduces four new variants of the async_schedule_ functions
that allow scheduling on a specific NUMA node.
The first two functions are async_schedule_near and
async_schedule_near_domain which end up mapping to async_schedule and
async_schedule_domain but provide NUMA node specific
