By: Anon (no.delete@this.spam.com), October 14, 2021 11:08 am
Room: Moderated Discussions
rwessel (rwessel.delete@this.yahoo.com) on October 14, 2021 9:01 am wrote:
> One of the concerns raised in earlier discussions was moving a running copy to a different core (possibly to
> a different machine in a cluster, or such). It appears this punts the problem of underlying different native
> move sizes to the OS fixing up an exception if the parameters end up incorrectly aligned on the new core.
Or the combination of two cores supporting different move sizes will be unsupported, is the combination of two cores with different cache line sizes supported to start with?
> One of the concerns raised in earlier discussions was moving a running copy to a different core (possibly to
> a different machine in a cluster, or such). It appears this punts the problem of underlying different native
> move sizes to the OS fixing up an exception if the parameters end up incorrectly aligned on the new core.
Or the combination of two cores supporting different move sizes will be unsupported, is the combination of two cores with different cache line sizes supported to start with?