On 2/9/24 12:31, Tony Luck wrote: > On Fri, Feb 09, 2024 at 09:27:56AM -0600, Moger, Babu wrote: >> Hi Tony, >> >> On 1/30/24 16:20, Tony Luck wrote: >>> This is the re-worked version of this series that I promised to post >>> yesterday. Check that e-mail for the arguments for this alternate >>> approach. >> >> To be honest, I like this series more than the previous series. I always >> thought RDT_RESOURCE_L3_MON should have been a separate resource by itself. >> >> You need to separate the domain lists for RDT_RESOURCE_L3 and >> RDT_RESOURCE_L3_MON if you are going this route. I didn't see that in this >> series. Also I have few other comments as well. > > They are separated. Each "struct rdt_resource" has its own domain list. Yea. You are right. > > Or do you mean break up the struct rdt_domain into the control and > monitor versions as was done in the previous series? No. Not required. Each resource has its own domain list. So, it is separated already as far as I can see. Reinette seem to have some concerns about this series. But, I am fine with both these approaches. I feel this is more clean approach. -- Thanks Babu Moger
