Date: Fri, 14 Feb 2014 01:22:34 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Ryan Stone <rysto32@gmail.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code? Message-ID: <CAJ-VmondWeDjSepQOmNtC1h7wZG=ZQax0tHPMv%2BSSc7O2KZ3dQ@mail.gmail.com> In-Reply-To: <CAJ-Vmommd7w_7RtkqgFGt%2BCVccqcsd8QLNOSXdXSRmmBPKEyYg@mail.gmail.com> References: <CAJ-Vmo=7Nz1jqXy%2BrTQ7u9_ZP7jeFOKUJxU1O51tYJjvTUmWTg@mail.gmail.com> <CAFMmRNxFbtegWMxfdD1=t7gHRVg_86FSxh0_R5_%2Bh5JP%2Bpw1Vw@mail.gmail.com> <CAJ-Vmommd7w_7RtkqgFGt%2BCVccqcsd8QLNOSXdXSRmmBPKEyYg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok, so now I remember the other odd thing. I was seeing the sending context(s) jumping from one CPU to another during flowtable_insert_common(), around the locking bits. But I thread pinned all the sender user threads! So, why would the senders still be scheduled on other CPUs if I've pinned the userland threads? (and yes, I verified that the userland threads weren't moving around.) -a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmondWeDjSepQOmNtC1h7wZG=ZQax0tHPMv%2BSSc7O2KZ3dQ>