-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vikunja namespaces #89
Comments
First, I would put every functionality, which is required for the implementation of the vikunja functions and which should normally not used by the user in an extra namespace, like the existing In my opinion the vikunja user namespace depends on the namespace of the algorithm, because I think it decides what the To make it easier to understand, I use the algorithm
My personal favorite is Option 3 and the |
Currently the vikunja has no clear concept for different namespaces. The main question is, how detailed or flat should be it?
Independent of the namespace question, I want to introduce the concept of
host
anddevice
:host
, if a device of the type accelerator can execute the non-vikunja c++-code. Typical the CPU of a computer.device
is a subset ofhost
. It can execute non-vikunja c++ code but don't need it.device
can be accessible from non-vikunja c++ code without memory copy but it is not requiredNote: CUDA virtual memory fulfill the requirements of host memory.
The text was updated successfully, but these errors were encountered: