processor affinity
hi
what is meant by processor affinity?
if somebody know anythiung about it?
or tell me the correct mailing list...
thanks
ankit
________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping"
your friends today! Download Messenger Now
http://uk.messenger.yahoo.com/download/index.html
Quoted 3 lines · Ankit Jain
hi
what is meant by processor affinity?
$ man sched_setaffinity
Signature · 3 lines
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan
Quoted 1 line · Ankit Jain
what is meant by processor affinity?
Affinity means that a process has an affinity for a particular subset of the available CPUs within a particular system - it wishes to run only on these processors. Linux supports hard processor affinity and process migration to enforce such demands which get be made using the POSIX sched_[set|get]param calls.
Robert Love has written an excellent book entitled Linux Kernel Development, it's not expensive and very worthwhile. Chapter 3 is entitled Scheduling and it explains process affinity as well as process migration and the concept of migration threads as used within the Linux kernel to enforce policy in the implmentation.
I suggest also that you consider joining the Kernel Newbies mailing list, newly revived and now with working signup page over at
http://www.kernelnewbies.org/
Jon.
Quoted 4 lines · Ankit Jain
hi
what is meant by processor affinity?
Quoted 8 lines
if somebody know anythiung about it?
or tell me the correct mailing list...
thanks
ankit
Its the ability to bind a process to subset of processors.
Neil
Quoted 7 lines
________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signature · 8 lines
/*************************************************** *Neil Horman *Software Engineer *Red Hat, Inc. *[email protected] *gpg keyid: 1024D / 0x92A74FA1 *http://pgp.mit.edu ***************************************************/
Ankit Jain wrote:
Here's a real good description in a patent owned by Novell on the subject.
Jeff
Quoted 22 lines
hi
what is meant by processor affinity?
if somebody know anythiung about it?
or tell me the correct mailing list...
thanks
ankit
________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 5 lines · Jeff V. Merkey
Here's a real good description in a patent owned by Novell on the subject.
Jeff
Wow, I never knew about that.
But guess who wrote the affinity system calls? :)
Robert Love
Quoted 12 lines · Robert Love
Quoted 7 lines · Jeff V. Merkey
Here's a real good description in a patent owned by Novell on the subject.
Jeff
Quoted 8 lines
Wow, I never knew about that.
But guess who wrote the affinity system calls? :)
Robert Love
I wrote them first, and coined the term.
:-)
Jeff
Quoted 3 lines
Quoted 6 lines · Jeff V. Merkey
Quoted 4 lines
Wow, I never knew about that.
But guess who wrote the affinity system calls? :)
I wrote them first, and coined the term.
Cute but GCOS3 had affinity syscalls for batch processing in the 1970's and I don't believe it was original even then.
Quoted 14 lines · Alan Cox
Quoted 8 lines · Jeff V. Merkey
Quoted 8 lines
Wow, I never knew about that.
But guess who wrote the affinity system calls? :)
Quoted 8 lines
Quoted 3 lines
I wrote them first, and coined the term.
Cute but GCOS3 had affinity syscalls for batch processing in the 1970's and I don't believe it was original even then.
Using them for Intel Cache affinity was new at the time. Intel SMP hardware was not readily available at the time and was in its infancy in 1993 when this was developed. This implementation (like Linux) was specific to IA32 architecture systems.
Jeff
Quoted 8 lines
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 4 lines · Jeff V. Merkey
Using them for Intel Cache affinity was new at the time. Intel SMP hardware was not readily available at the time and was in its infancy in 1993 when this was developed. This implementation (like Linux) was specific to IA32 architecture systems.
The Linux implementation works on about a dozen plattforms, or how many smp ports we have these days..
Quoted 14 lines · Christoph Hellwig
Quoted 4 lines · Jeff V. Merkey
Using them for Intel Cache affinity was new at the time. Intel SMP hardware was not readily available at the time and was in its infancy in 1993 when this was developed. This implementation (like Linux) was specific to IA32 architecture systems.
The Linux implementation works on about a dozen plattforms, or how many smp ports we have these days..
In it's early beginnings, Linux was IA32 based. A pretty cool idea at the time. The patent took ten years to issue due to all the prior
art claims. I remember Novell's lawyers bringing me reams of prior art to review during the initial work to verify there was no prior
art in the field. Apparently, this was for first affinity patent on SMP architecture systems filed, or it would not have issued. Anyway, I provided it as a reference since it is the first patent on SMP affinity scheduling and methods for the very interested person who asked. And yes, Linux appears to infringe it, but since Novell is pro-Linux, I don't think it matters.
:-)
Jeff
Quoted 6 lines · Jeff V. Merkey
Anyway, I
provided it as a reference since it is the first patent on SMP affinity scheduling and methods for the very interested person who asked. And yes, Linux
appears to infringe it, but since Novell is pro-Linux, I don't think it matters.
Still it's probably worth knowing it might be an issue someday. What's Novell's position on patents they hold involving the kernel? I'm too lazy to go hunting for it (rml might well know).
Jon.
Quoted 13 lines · Jon Masters
Quoted 8 lines · Jeff V. Merkey
Anyway, I
provided it as a reference since it is the first patent on SMP affinity scheduling and methods for the very interested person who asked. And yes, Linux
appears to infringe it, but since Novell is pro-Linux, I don't think it matters.
Quoted 8 lines
Still it's probably worth knowing it might be an issue someday. What's Novell's position on patents they hold involving the kernel? I'm too lazy to go hunting for it (rml might well know).
Jon.
Since they are hiring as many top Linux folks as possible, and they have invested their entire future in Linux, I think their actions speak so loud, it doesn't matter what your hearing from them. Novell's position (from my experience) it that they will take whatever steps they feel necessary to protect their circle (as evidenced by an illegal search of my home by Novell Security Employees (not law enforcement 8 Novell employees and a sheriff) ) along with spending 17 million dollars in litigation costs to keep me out of the computer business for almost 4 years by crushing me, my family, and any business I tried to start, and ruining my life and my marriage with my previous wife of 24 years).
If you are in their circle, they will fight for you to the death, and breaking the rules doesn't bother them. If you are outside their circle ........ you should feel very safe and comfortable.
Linux is in their circle at present. I think you should weigh the options and make the appropriate decisions when choosing to deal with them.
Jeff
Quoted 2 lines · Jeff V. Merkey
Since they are hiring as many top Linux folks as possible, and they have invested their entire future in Linux, I think their actions speak so loud,
I only asked because I'd not heard of an official patent position from them (but I've not looked) and I wondered if someone happened to know
- words are completely meaningless.
<snip>
Wow, tha'ts one bitter mail you sent. Sorry to hear about it but I'd rather not start a general discussion about big business practices and Novell - just interested in the patent situation.
Jon.
Quoted 13 lines · Jon Masters
Quoted 4 lines · Jeff V. Merkey
Since they are hiring as many top Linux folks as possible, and they have invested their entire future in Linux, I think their actions speak so loud,
I only asked because I'd not heard of an official patent position from them (but I've not looked) and I wondered if someone happened to know
- words are completely meaningless.
Quoted 10 lines
<snip>
Wow, tha'ts one bitter mail you sent. Sorry to hear about it but I'd rather not start a general discussion about big business practices and Novell - just interested in the patent situation.
Jon.
Just letting you have a little insight into what their position might be. It's not bitter, it's factual, and I got over Novell a long time ago. They will probably ignore you for now, but in the future, if Linux contains IP from sources they consider theirs, it would be possible for them to shut out competitors without a license from them. Not only on this topic, but any other area their employees have contributed for which they hold patents. This case may be a special one, but anytime you use patented materials are even areas where there is a doubt there is exposure. I have a release from them and I can use any IP I retained in a non-tangible form that would have been theirs. So I can use this patent without concern of infringement claims. But since I did not instrument the affinity code in Linux, it's not protected this way. NWFS is protected this way and people can use it without fear of claims from Novell.
Jeff
Quoted 20 lines · Jeff V. Merkey
Quoted 18 lines · Alan Cox
Quoted 13 lines · Jeff V. Merkey
Quoted 8 lines
Wow, I never knew about that.
But guess who wrote the affinity system calls? :)
I wrote them first, and coined the term.
Quoted 7 lines
Quoted 4 lines
Cute but GCOS3 had affinity syscalls for batch processing in the 1970's and I don't believe it was original even then.
Using them for Intel Cache affinity was new at the time. Intel SMP hardware was not readily available at the time and was in its infancy in 1993 when this was developed.
That is amazingly specific - I suppose using it for cache affinity on earlier processors wouldn't count :)
Joking aside, this doesn't seem like it would apply to Linux's scheduler. We don't use a global queue, and we don't implement hard affinities with local queues, but with a specific bitmask of cpus.
Of course, I don't really have any idea how to interpret patents...
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 3 lines · [email protected] wrote:
Quoted 1 line · Nick Piggin
Of course, I don't really have any idea how to interpret patents...
^^^
keeping that in mind
Quoted 3 lines
The implementation in NetWare and the Implementation in Linux are similiar but not identical, but they are close enough. CPU bitmasks were used. The best apporach would be for someone to locate prior art in the field and challenge the patent in the event any claims were ever brought or avoid the same methods.
It seems that the actual patent describes the implementation of the scheduler that achieves this. And in it, the method used is a locked global queue and unlocked local queues. But anyway.
Quoted 1 line
I was able to achieve greater than 100% scaling per processor due to Intel's quirky cache behavior.
And probably most cache behaviours. If you have a set of tasks with a working set larger than the cache of 1 processor but that can be divided to fit into the cache of 2, then you're laughing.
More than 1 CPU can dramatically lower task switch (and mm switch) rates in ideal situations, too.
Quoted 6 lines
If you can get a small subset of code in the cache controllers for processes through hueristics (i.e. guessing) additive processor scaling can be increased dramatically due to taking advantage of the L1 and L2 proceesor caches. Linux is somewhat crude
from an SMP perspective even today, although it has an impressive
array of hardware support for SMP systems and architectures, but based on the small number of processes than run on average (< 100)
this technique would work on Linux.
Well it has pretty strong CPU affinity, and roughly distributes load evenly over CPUs. What more do you want? :)