GPU stride/destride can be done on device

[johnlees]

It may be more efficient to replace the stride_copy/destride_copy functions with a kernel which destrides, then copy the result back. This works naturally in the case of the filter history as the D->D copy would be replaced with a kernel call. For functions in the dust object, some scratch space on the device would be needed.