pprokop

I just don't know how this information provided via attributes can be useful to custom scheduler without mapping to already used cpus. NRT object only exposes info about allocated/free cpus...

I still feel like this information should be then exposed via labels and just say that given node has `e` or `p` cores without the numbers. And then no special...

/lgtm

/lgtm

I don't think that's the right place to fix it as later call to `updateAvailable` will ignore the resource not present during startup here -> https://github.com/kubernetes-sigs/node-feature-discovery/blob/master/pkg/resourcemonitor/noderesourcesaggregator.go#L246

@ozhuraki please add unit test for this functionality. I'll try to review more in depth today/tomorrow.