-
Notifications
You must be signed in to change notification settings - Fork 1
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
Storage of (t,s,d) Triplets in OutRegistry #76
Comments
In fact, the solution outlined above would not work: owing to the way the OutRegistry interface is defined, it is necessary for it to have a statically defined list of all possible triplets. As an alternative, we could characterize each out-going report/command through four data: (t,s,d1,d2). Here (t,s) are the type and sub-type of the report/command and d1/d2 are one of the following:
|
The following solution has been implemented. Each out-going report/command in the OutRegistry is characterized through four data: (t,s,d1,d2). Here (t,s) are the type and sub-type of the report/command and d1/d2 are one of the following:
|
Each out-going report/command in the OutRegistry is characterized through four data: (t,s,d1,d2). Here (t,s) are the type and sub-type of the report/command and d1/d2 are one of the following: - They are both zero if the pair (t,s) has no discriminant - They are the minimum and maximum value of the discriminant
The OutRegistry keeps track of the enable status of each (type,subtype,discriminant) triplet. For this purpose, it needs a data structure where this information is stored. The data structure must be easily searchable.
The current implementation is wasteful of memory because it allocates to each (t,s) pair N bits where N is the maximum value of the discriminant for reports of type (t,s).
Marcel has proposed the following solution:
The text was updated successfully, but these errors were encountered: