Well, Ingo plans to have it merged by the end of the year so I guess you can wait.
As a side note I've been running it on my Thinkpad for a couple of months now and
haven't run into any issues.
I'm of the mindset that if you *know* of these specific latencies and what workloads are causing them and care so dearly about them, you should probably be savey enough to apply the -rt patch. And which work loads would you be referring to?
You should realize that CFS was built around the -rt patch The -rt patch will:
Make latencies deterministic
Reduce latencies if used correctly
Add slight over head to overall througput
I think once the -rt patch is merged into the mainline it will work wonders
for games and all sorts of other important things, like industrial automation,
automated stock trading, and other high-speed data acquisition and processing.
So there is a road map to improve scheduling. In fact it's actually a broader and
more appealing plan than just scheduling for the desktop, IMHO. I think this is what
Linus is trying to get at in terms of his why he doesn't want a perfect desktop scheduler.
Not even the reputations of maintainers called "the high priests of the Linux kernel team" by Alioth, who are likely to point out what they consider as fundamental problems with the concept behind a given patch, reject the patch, and claim to plan to reject any similar patch?
I never said that the kernel maintainers would accept said patch, I merely meant to point out that if it was a grand idea(referring to parent and *not* UIO)
that it would be accepted into the mainline based on its technical merits. I was not opposing the UIO patch in any way shape or form. I think you misunderstood me. I'm all for UIO. Especially since I'm trying to persuade my current employer to look into embedded Linux as a OS solution since we are a smaller integration company with limited resources to develop our own OS.
But it does help embedded developers who need access to an SOC's hardware like PWM and GPIO and A2D.
A lot of people really are missing the point here that this patch really doesn't do much for x86, but
does great things for SuperH PPC and ARM.
They impression that I get is that this is in order to use SOC's more effectively. Things like using PWM and GPIO on SOC's aren't that portable across different brands of micros. This would be an easy way for all the SOC chip makers (Freescale, Atmel, Renesas, Marvell, ect...) to create the bottom level of the driver and use the same userspace driver for embedded developers. this will still give the developers enough leway to mess with things if they need to. I could be totally off though...
"You're being screwed by monopolists while being told you're in a free market."
That's where your wrong. You are only screwed by monopolists if you buy their product. Judging from what you are asserting those products would be iPods, mobile phones(and services?), and I'm guessing Operating Systems?
While I agree monopoly is bad, there is only one way to fight them as a private citizen with limited resources: DON'T BUY THEIR SHIT. Those products are luxury items, THAT YOU DO NOT NEED TO LIVE.
And about your assertion that an Athenian or Roman had nothing to worry about and could just up and go whenever they wanted... What about food and shelter? Seems to me like the citizenry of those days were a slave to their own survival. Which is no different than the working class these days. In fact, I maintain that the Athenians and Romans had more to worry about than any citizen of the well-fare state that the US has become.
The thing that is causing your 'bonding' of the working middle class is the very same thing relieving the poor of their bondage. I wonder why that is?
Great... So any security holes the Samba team fixes from here on out MS won't be able to use?
YAY Microsoft FTW! Ultimately that would still mean they take on a GPLv2 project so still a win
for FOSS in my book. But its far more likely that they would re-engineer.
Samba moved to GPLv3.
So unless Microsoft wants to start it's own SMB/CIFS networking protocol from scratch in the Linux
environment they have to sanction and help a GPLv3 project in the name of interoperability.
Jeremy Allison is no ones fool.
Actually after the second round of drill questions and the take home work I told them I really didn't feel like jumping through their hoops over the phone (who wants to work for a company that treats people that way?). So I went with a company that was willing to talk to me face to face (e.g. flew me out to their base of operations for a meet and greet)
Wouldn't these count for Prior art... I didn't get to read the whole patent (have to run for work)
but it seems to me that to many companies are using obviousness in their claims and are trying to
patent the 'stack' of ideas, which is really obvious given that they are just using standard tools
to make a product so why make claims like this in the patent:
75. The computer-accessible medium as recited in claim 74, wherein receiving said given client request according to said web services protocol includes receiving a document encapsulated according to a version of Simple Object Access Protocol (SOAP), wherein contents of said given client request are included in said document and formatted according to a version of XML.
As far as Linux Wifi goes I've always gone ipw and never had a problem...
But I have to say... when Debian makes you install firmware from 'non-free'
it does make you feel like you are killing kittens... or masturbating... or errr....
Well, Ingo plans to have it merged by the end of the year so I guess you can wait.
As a side note I've been running it on my Thinkpad for a couple of months now and
haven't run into any issues.
I'm of the mindset that if you *know* of these specific latencies and what workloads are causing them and care so dearly about them, you should probably be savey enough to apply the -rt patch. And which work loads would you be referring to?
The -rt patch will:
- Make latencies deterministic
- Reduce latencies if used correctly
- Add slight over head to overall througput
I think once the -rt patch is merged into the mainline it will work wondersfor games and all sorts of other important things, like industrial automation,
automated stock trading, and other high-speed data acquisition and processing.
So there is a road map to improve scheduling. In fact it's actually a broader and
more appealing plan than just scheduling for the desktop, IMHO. I think this is what
Linus is trying to get at in terms of his why he doesn't want a perfect desktop scheduler.
But it does help embedded developers who need access to an SOC's hardware like PWM and GPIO and A2D.
A lot of people really are missing the point here that this patch really doesn't do much for x86, but
does great things for SuperH PPC and ARM.
...or applying patches for the scheduler and what not...
http://www.osadl.org/UIO.uio.0.html
They impression that I get is that this is in order to use SOC's more effectively. Things like using PWM and GPIO on SOC's aren't that portable across different brands of micros. This would be an easy way for all the SOC chip makers (Freescale, Atmel, Renesas, Marvell, ect...) to create the bottom level of the driver and use the same userspace driver for embedded developers. this will still give the developers enough leway to mess with things if they need to.
I could be totally off though...
No one is stopping you from implementing it yourself and submitting it to the main line.
You mean the fight for patent free software is like the fight for free speech... Isn't that quaint.
You should probably read The Innovator's Dilemma.
Or maybe just read about the concepts presented in the book.
"Is Microsoft hurting? Perhaps, but I don't believe they've been sending out large numbers of pink slips to their employees."
No but they are having a hard time finding new employees
"You're being screwed by monopolists while being told you're in a free market."
That's where your wrong. You are only screwed by monopolists if you buy their product. Judging from what you are asserting those products would be iPods, mobile phones(and services?), and I'm guessing Operating Systems?
While I agree monopoly is bad, there is only one way to fight them as a private citizen with limited resources: DON'T BUY THEIR SHIT. Those products are luxury items, THAT YOU DO NOT NEED TO LIVE.
And about your assertion that an Athenian or Roman had nothing to worry about and could just up and go whenever they wanted... What about food and shelter? Seems to me like the citizenry of those days were a slave to their own survival. Which is no different than the working class these days. In fact, I maintain that the Athenians and Romans had more to worry about than any citizen of the well-fare state that the US has become.
The thing that is causing your 'bonding' of the working middle class is the very same thing relieving the poor of their bondage. I wonder why that is?
Great... So any security holes the Samba team fixes from here on out MS won't be able to use?
YAY Microsoft FTW! Ultimately that would still mean they take on a GPLv2 project so still a win
for FOSS in my book. But its far more likely that they would re-engineer.
That all depends... Some of the Kernel code is GPLv2 or later.
Samba moved to GPLv3.
So unless Microsoft wants to start it's own SMB/CIFS networking protocol from scratch in the Linux
environment they have to sanction and help a GPLv3 project in the name of interoperability.
Jeremy Allison is no ones fool.
Who let the SCO troll in?
Why do you need freedom? If you have to ask you will never know...
99.9999% of the people who make assertions about 99.9999% of anything are wrong 99.9999% of the time.
...it this case there is more than meets the eye....
Actually after the second round of drill questions and the take home work I told them I really didn't feel like jumping through their hoops over the phone (who wants to work for a company that treats people that way?). So I went with a company that was willing to talk to me face to face (e.g. flew me out to their base of operations for a meet and greet)
Well that's just what I wanted to hear... more horse-shit... And to think, I interviewed with these fucktards...
but it seems to me that to many companies are using obviousness in their claims and are trying to
patent the 'stack' of ideas, which is really obvious given that they are just using standard tools
to make a product so why make claims like this in the patent:
Honestly, why not try to pattent using C++ for making applications...
I'm not sure how much of this is covered but here might be some Prior Art:
http://eyeos.org/about
http://gizmodo.com/gadgets/cheap-pc/zonbu-to-roll
show us your references... (I feel like this is a common theme from somewhere...)
As far as Linux Wifi goes I've always gone ipw and never had a problem...
But I have to say... when Debian makes you install firmware from 'non-free'
it does make you feel like you are killing kittens... or masturbating... or errr....
I would mod up that comment ... but what's the point in modding an AC =P
Instead I'll just say: good job.