Searched hist:"8 d5f3a2bdbd5493c76c53c9a806b148b95799bbb" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | paths.hpp | diff 8d5f3a2bdbd5493c76c53c9a806b148b95799bbb Tue Jul 07 10:30:33 CDT 2020 Matt Spinler <spinler@us.ibm.com> PEL: Add PEL repository capping related fields
If not capped, the PEL repository would keep taking up more and more
space as more PELs are added. In preparation for handling this, add
a field to the Repository class to track the total size that all PELs can
take up and a field to track the maximum number of PELs that can be
stored.
The size value is hardcoded to be 20MB (and 100KB in unit test), though
a Repository class constructor allows the number to use to be passed in.
The max number of PELs field is hardcoded to 3000 (100 in test) and this
can also be changed in the constructor.
In the future if different systems or configurations require different
values, then this could be set at configure time. This isn't done now
because I want to only add PEL options to the common phosphor-logging
configure.ac if absolutely necessary as the majority of phosphor-logging
users don't use PELs.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I72609a727229f96bd8ac23a630f25fd8b5c73427
|
| H A D | repository.hpp | diff 8d5f3a2bdbd5493c76c53c9a806b148b95799bbb Tue Jul 07 10:30:33 CDT 2020 Matt Spinler <spinler@us.ibm.com> PEL: Add PEL repository capping related fields
If not capped, the PEL repository would keep taking up more and more
space as more PELs are added. In preparation for handling this, add
a field to the Repository class to track the total size that all PELs can
take up and a field to track the maximum number of PELs that can be
stored.
The size value is hardcoded to be 20MB (and 100KB in unit test), though
a Repository class constructor allows the number to use to be passed in.
The max number of PELs field is hardcoded to 3000 (100 in test) and this
can also be changed in the constructor.
In the future if different systems or configurations require different
values, then this could be set at configure time. This isn't done now
because I want to only add PEL options to the common phosphor-logging
configure.ac if absolutely necessary as the majority of phosphor-logging
users don't use PELs.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I72609a727229f96bd8ac23a630f25fd8b5c73427
|
| H A D | repository.cpp | diff 8d5f3a2bdbd5493c76c53c9a806b148b95799bbb Tue Jul 07 10:30:33 CDT 2020 Matt Spinler <spinler@us.ibm.com> PEL: Add PEL repository capping related fields
If not capped, the PEL repository would keep taking up more and more
space as more PELs are added. In preparation for handling this, add
a field to the Repository class to track the total size that all PELs can
take up and a field to track the maximum number of PELs that can be
stored.
The size value is hardcoded to be 20MB (and 100KB in unit test), though
a Repository class constructor allows the number to use to be passed in.
The max number of PELs field is hardcoded to 3000 (100 in test) and this
can also be changed in the constructor.
In the future if different systems or configurations require different
values, then this could be set at configure time. This isn't done now
because I want to only add PEL options to the common phosphor-logging
configure.ac if absolutely necessary as the majority of phosphor-logging
users don't use PELs.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I72609a727229f96bd8ac23a630f25fd8b5c73427
|