Open jjwilke opened 7 years ago
this is easy enough to change; the harder part is propagating that information piece-wise to the backend. I would need a few more methods on SerializationManager
to tell the backend something isn't serializable (and I would need to propagate this information up to Task::is_migratable()
). Still, shouldn't take long.
I'm not sure we even need to work that hard at it. The backend should just globally be running in a "no serialization" mode. This doesn't need to be piece-meal with some tasks migratable and others not. This is entirely a serialization allowed, not allowed.
Low priority.
From: David Hollman notifications@github.com<mailto:notifications@github.com> Reply-To: DARMA-tasking/darma-frontend reply@reply.github.com<mailto:reply@reply.github.com> Date: Tuesday, March 21, 2017 at 5:00 PM To: DARMA-tasking/darma-frontend darma-frontend@noreply.github.com<mailto:darma-frontend@noreply.github.com> Cc: "Wilke, Jeremiah J" jjwilke@sandia.gov<mailto:jjwilke@sandia.gov>, Author author@noreply.github.com<mailto:author@noreply.github.com> Subject: [EXTERNAL] Re: [DARMA-tasking/darma-frontend] serialization interface not required for quick prototyping on-node (#9)
this is easy enough to change; the harder part is propagating that information piece-wise to the backend. I would need a few more methods on SerializationManager to tell the backend something isn't serializable (and I would need to propagate this information up to Task::is_migratable()). Still, shouldn't take long.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/DARMA-tasking/darma-frontend/issues/9#issuecomment-288257077, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAGh2SkhfY1uGWnyvFeWcTp0cYCMlLAVks5roGSYgaJpZM4Mkjny.
We should still require this by default, but there should be a way to turn off this requirement (via ifdefs or something created by configure) if I want to quickly implement something that doesn't require serialization functionality. On-node tasking only.