Re: [PATCH v2] sched: update_top_cache_domain only at the times of building sched domain.

[Michael Wang <wangyun@linux.vnet.ibm.com>]

On 07/24/2013 09:57 PM, Rakib Mullick wrote:
> On Wed, Jul 24, 2013 at 2:34 PM, Michael Wang
[snip]
>>
>> I think you missed this in PeterZ's suggestion:
>>
>> -               cpu_attach_domain(NULL, &def_root_domain, i);
>>
>> With this change, it will be safe since you will still get an un-freed
>> sd, although it's an old one.
>>
> I never meant it and clearly I missed it. If you remove
> cpu_attach_domain(), then detach_destroy_domain() becomes meaningless.
> And I don't have any intent to remove cpu_attach_domain from
> detach_destroy_domain() at all.
> 
>> But your patch will run the risk to get a freed sd, since you make
>> 'sd_llc' wrong for a period of time (between destroy and rebuild) IMO.
>>

Ok, allow me try to explain it again, hope this time it could be more
clear...

> Building 'sd_llc' depends on schedule domain. If you don't have sd,
> sd_llc will point to NULL and sd_llc_id is
> the CPU itself. Since, we're  trying to re-construing so for this time
> being it doesn't matter, cause we're building
> it again. 

It does matter, although we build it again, we need to make things sync
at any point of time in SMP world.

Now, please just note what you're saying, on last thread
> you've said -
> 
>        "I don't think we have the promise that before we rebuild the stuff
>         correctly, no one will utilize 'sd_llc'..."
> 
> If that is the case, then we shouldn't worry about it at all. And this
> above comments (from previous thread I've quoted and this thread I'm
> replying) they're just self contradictory.

Let's have some picture like:

	destroy
		cpu_attach_domain(NULL)			//cad_A
			update_top_cache_domain()	//utcd_A

	WINDOW	//begin after last rcu_read_unlock()
		//end after next rcu_read_lock()

	build
		cpu_attach_domain(new_sd)		//cad_B
			update_top_cache_domain()	//utcd_B

Now in old world, what we have is:
1. in 'utcd_A', make 'sd_llc' to be NULL since old_sd was destroyed in
cad_A.
2. thus during WINDOW, both 'rq->sd' and 'sd_llc' is NULL
3. in 'utcd_B', update 'sd_llc' to be the new 'highest cache-share sd'
since new_sd attached in 'cad_B'

Now with your patch applied, what will happen is:
1. 'utcd_A' won't happen now, although the sd 'sd_llc' point to was
destroyed in 'cad_A'
2. thus during WINDOW, 'rq->sd' is NULL while 'sd_llc' is the destroyed
'old highest cache-share sd'
3. in 'utcd_B', update 'sd_llc' to be the new 'highest cache-share sd '
since new_sd attached in 'cad_B'

Seems like both will result the same 'sd_llc', but your patch make
'sd_llc' point to a destroyed sd during the WINDOW.

And I said:

"I don't think we have the promise that before we rebuild the stuff
correctly, no one will utilize 'sd_llc'..."

By which I mean some one will utilize 'sd_llc' during the WINDOW, in old
world, it's safe since will get NULL, with your patch, it's unsafe since
we get a freeing sd.

And that's the risk I concerned, and that's my point.

> 
>> I guess I get you point, you are trying to save one time update since
>> you think this will be done twice, but actually the result of this two
>> time update was different, it's not redo and it's in order to sync
>> 'sd_llc' with 'rq->sd'.
>>
> Yes, you got my point now, but I don't understand your points. Anyway,
> I'm not going to argue with this
> anymore, this stuff isn't much of an issue, but removing this sorts of
> stuff is typical in kernel development.

I'm not argue, actually there is nothing to argue...just try to explain
what is wrong IMO, if I failed to, then I could only blame my poor
writing skill...

Regards,
Michael Wang

> 
> Thanks,
> Rakib.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>