I believe you can use lockOSThread to pin a processor to the current thread, then use native code to pin the thread to a particular processor, change its priority, etc. I haven’t tried it but I see no reason it wouldn’t work - similar to how it’s not supported in Java but you can still do it - watch out for priority inversion and scheduling deadlocks !
> On May 9, 2019, at 3:31 AM, Nitish Saboo <nitish.sabo...@gmail.com> wrote: > > Hi Kurtis, > > Thanks for the clarification .initialize_engine() is a C code and is being > called from go method 'initialize()'. > If you see my reply 2 mails before, 'initialize_engine()` method starts a > syslog-ng engine but does not return the instance of it. > And therefore there was a confusion if calling 'initialize_engine' twice is > actually instantiating two independent syslog-ng instances or not. > > Thanks > > >> On Thu, May 9, 2019 at 11:12 AM Kurtis Rader <kra...@skepticism.us> wrote: >>> On Wed, May 8, 2019 at 10:17 PM Nitish Saboo <nitish.sabo...@gmail.com> >>> wrote: >> >>> Yes, I want (exactly) two instances of syslog-ng engines running since I >>> initialised the engine twice.And I guess it is possible only when the >>> syslog-ng engines are running on two different processors.I might be wrong >>> here, please correct me if my understanding is not right. >>> My goal right now is how to verify if two independent syslog-ng engines are >>> getting initialised or not ? >>> Once this verification is done, Can we hook instance 'a' to syslog-ng >>> engine on processor 'a' and instance 'b' to syslog-ng engine on processor >>> 'b'. >> >> There may be a human language barrier here in as much as my native language >> is English and I suspect your native language is something else. Whether or >> not you instantiate two distinct syslog-ng engines is unrelated to which >> CPUs (processors) each runs on. There is no way, in general, for the Go >> scheduler to know which CPU a goroutine is running on. Nor is there any way >> to bind a goroutine to a specific CPU as far as I know. You could (in >> theory) create two distinct instances of the syslog-ng engine and they could >> still execute on the same CPU. If or no other reason than that your system >> only has a single CPU core available for your process. >> >> > I hope I am able to clarify my thinking here. >> >> No, sorry, you have not. If anything every reply you make increases the >> confusion about what you are trying to do. If your `initialize_engine()` >> method always instantiates, and returns, a new instance of the "syslog-ng" >> engine then the two Go objects initialized by that call will be two >> independent instances of that engine. Assuming, of course, that your >> syslog-ng engine does not share state between distinct `initialize_engine()` >> calls. >> >> -- >> Kurtis Rader >> Caretaker of the exceptional canines Junior and Hank > > -- > 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 discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/CALjMrq7jyZmDEwTxbQ-m-WUubP-A2_QWw-8UZhUbi%2BcLd1wpOQ%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/2891AEAD-B5DB-4D77-9D78-716EF02A14AC%40ix.netcom.com. For more options, visit https://groups.google.com/d/optout.
