David Hildenbrand <da...@redhat.com> writes: > Thanks Markus! > >> I just tested again, and get the same result as you. I figure my >> previous test was with the complete series. >> PATCH 5 appears to make it work. Suggest to say something like "The >> commit after next will make this work". > > I'll phrase it like " We'll wire this up next to make it work."
Works for me! > [...] > >>>> So, when a thread is created, its affinity comes from its thread context >>>> (if any). When I later change the context's affinity, it does *not* >>>> affect existing threads, only future ones. Correct? >>> >>> Yes, that's the current state. >> >> Thanks! > > I'm adding > > "Note that the CPU affinity of previously created threads will not get > adjusted." > > and > > "In general, the interface behaves like pthread_setaffinity_np(): host CPU > numbers that are currently not available are ignored; only host CPU > numbers that are impossible with the current kernel will fail. If the list of > host CPU numbers does not include a single CPU that is > available, setting the CPU affinity will fail." This is one of the reasons why reviewing your work is such a pleasure: not only do you answer my questions with clarity and patience, you proactively improve your patches before I can even think to ask. Thank you!
