在 2019年7月31日星期三 UTC+8下午12:08:51,Ian Lance Taylor写道:
>
> On Tue, Jul 30, 2019 at 8:58 PM >
> wrote:
> >
> > I read go runtime code,but I'm poor in assembly language,
> > i can't understand the following code
> > // switch to g0
> > MOVQDX, g(CX)
> > MOVQ(g_sc
so mstart just put on stack for call traceback , but actually will not
return at mstart?
在 2019年7月31日星期三 UTC+8下午12:08:51,Ian Lance Taylor写道:
>
> On Tue, Jul 30, 2019 at 8:58 PM >
> wrote:
> >
> > I read go runtime code,but I'm poor in assembly language,
> > i can't understand the following co
Thank you very much.
在 2019年7月31日星期三 UTC+8下午9:49:04,Ian Lance Taylor写道:
>
> On Wed, Jul 31, 2019 at 4:49 AM jin wang > wrote:
> >
> > so mstart just put on stack for call traceback , but actually will not
> return at mstart?
>
> Yes. As you can see, the sy
why p's local run queue size is 256, not 128 or 512?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discus
Thank you very much, it's a fact that he change was 6 years ago, it's a
pity can't get that benchmark code.
在 2020年1月26日星期日 UTC+8下午11:55:01,Ian Lance Taylor写道:
>
> On Sun, Jan 26, 2020 at 2:31 AM jin wang > wrote:
> >
> > why p's local run queue size
I find it, thank you.
在 2020年1月27日星期一 UTC+8下午2:30:03,Ian Lance Taylor写道:
>
> On Sun, Jan 26, 2020 at 5:48 PM jin wang > wrote:
> >
> > Thank you very much, it's a fact that he change was 6 years ago, it's a
> pity can't get that benchmark code.
&
the run queue from the tail by other Ps, 256 run queue size
> prevents false sharing when the work-steal happens on different cores.
>
> On Sunday, January 26, 2020 at 6:31:27 PM UTC+8, jin wang wrote:
>>
>> why p's local run queue size is 256, not 128 or 512?
>>
ores.
>
> On Sunday, January 26, 2020 at 6:31:27 PM UTC+8, jin wang wrote:
>>
>> why p's local run queue size is 256, not 128 or 512?
>>
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from th