Last time I read anything about it (which was years ago) the Linux cache aware scheduling consisted of trying to get task scheduled on the same processor as they were scheduled on previously. This works well for a lot of things, but you lose a lot of benefit when multiple simultaneous tasks are working on the same data since those tasks would be spread across the processors to take advantage of concurrency.
This is just an engineering trade off.
Actually it may be a very good thing if this case were to reach the Supreme Court since the justices aren't are more likely to make the correct decision when Christianity isn't involved. Religious freedom is easier to appreciate when you're own religion doesn't have the upper hand.
It starts out as text base and then as the download progresses you'll start to get crude low polygon monochrome wire frames with only PC speaker beeps. Eventually you'll get to high polygon count fully textured and shaded 3D graphics with surround sound.
Besides, this only works either temporarily or in discrete locations. If the whole world gets misty it's going to be humid and feel hot and sticky. Also, since there's no way that the water vapor and clouds (back to mist again) would stay uniformly distributed, this will probably make for some very powerful storms.
has nothing to do with computers. The source of the problem is the source of money. Who decides how much money there is?
I want to decide how much money there is.
Who reaps the benefits of creating money which is not backed by real productivity?
I can do that too!
If you're truly looking for the root of the problem instead of symptoms, then you have to find out about the inner workings of the money system.
Root of the problem is being comfortable living (or operating) on credit, and even though it has tax benefits (in the US) it's interests (well, not with the new US interest rate) and risks should be enough to scare people.
A lot of the complexities are the results of the rules imposed on banks, though the banks do have lobbiest.
As far as mixing account types into one account -- you can usually mix savings and checking (AKA checking with interest) but there will be interest or higher minimum balance rules.
Many banks also offer various forms of overdraft protection, many of which are essentially a line of credit, though usually with a sharp penalty.
Lenders who lend someone else's money need to know how long they long they can use that money and depositers need to know how long they might have to wait to get their money back. That is why a 5 year CD has a greater interest rate than a 3 month CD. Banks make assumptions that checking account deposits must stay fairly liquid, savings account deposits semi-liquid, and CDs are solid until they mature (relative to the depositor of course)
Keeping buckets of money separate and labeled is good.
Lending is the flip side of that; knowing how long money is lent for is important to planning, meeting regulations, and covering transaction costs.
Their's also the rules about how a loan is repaid (lump sum, periodic payments,...). All of these things make different loan accounts different.
Most cell providers allow you to send SMS from a websites (eg. vtext.com for Verizon) and on that you input the sending numbers, so if the actual sending numbers are used that is exactly no protection against anything except an idiot who uses his real number to wrongly try to remotely disable a laptop or DOS it.
It's a giant game of chicken between the ISPs. They all know that they can't individually block Google or their users would raise Hell and try to move to a different ISP, and ISPs that didn't block Google would win BIG.
What they are really trying to do is hide part of the expense of being an ISP from the client users (homes and small businesses) who can more easily change their ISP to content providers who would be forced to pay to reach the people.
If this happens you'll end up with nearly free Internet service in competitive locations, but the barrier for entry for content providers will become impossibly high.
If I were a betting man I'd bet that much of what is being reported as living in a page file is likely also still in RAM, but that RAM is ready to be used either for something new or for it's current contents (mirror of what's in the page file).
It's likely that there's a bunch of stuff in each process that gets used very infrequently so the OS sees that it hasn't been changed in a while and goes ahead and puts it on the disk so that if/when that RAM is needed for something else the current contents will already be saved and no disk delay will be incurred in repurposing that RAM.
You might want to try replacing many programs as you can with busybox. It's versions of utilities are less complete than the standard gnu utilities, but they are all rolled into one binary, so most likely most of that binary will get cached in ram pretty early and stay there.
Also, for any packages you build you should try to use the -Os option for gcc, and perhaps even strip the binaries to remove unused symbols and debug info.
Building the system as though this was an embedded system with a small disk should be a win in most cases since fewer things have to go over the wire to load a file and more of the binaries can fit into cache.
What if you were to release said project under a FOSS license before the meeting where you are supposed to sign over the rights to it, and then inform the university's legal department of that and how it is now impossible to sign over the exclusive rights to your project to them?
Or get them to agree to a FOSS license?
That is unless you don't want it to be FOSS, but you could still sell a friend a license to it before signing over the rights. Of course you may end up being told "well you'll have to do another project that we do get the exclusive rights to". Go talk to a lawyer.
So you wanted people to leave their computers on all weekend? You must hate the environment.
Then how are actual damages for GPL violations calculated?
Last time I read anything about it (which was years ago) the Linux cache aware scheduling consisted of trying to get task scheduled on the same processor as they were scheduled on previously. This works well for a lot of things, but you lose a lot of benefit when multiple simultaneous tasks are working on the same data since those tasks would be spread across the processors to take advantage of concurrency.
This is just an engineering trade off.
... who actually benefits the most from botnet existing.
Of course. It's so obvious now. It was Lou Diamond Philips all along.
Actually it may be a very good thing if this case were to reach the Supreme Court since the justices aren't are more likely to make the correct decision when Christianity isn't involved. Religious freedom is easier to appreciate when you're own religion doesn't have the upper hand.
It starts out as text base and then as the download progresses you'll start to get crude low polygon monochrome wire frames with only PC speaker beeps. Eventually you'll get to high polygon count fully textured and shaded 3D graphics with surround sound.
So this guy has patented mist-ers in quantity?
Besides, this only works either temporarily or in discrete locations. If the whole world gets misty it's going to be humid and feel hot and sticky. Also, since there's no way that the water vapor and clouds (back to mist again) would stay uniformly distributed, this will probably make for some very powerful storms.
is goatse
has nothing to do with computers. The source of the problem is the source of money. Who decides how much money there is?
I want to decide how much money there is.
Who reaps the benefits of creating money which is not backed by real productivity?
I can do that too!
If you're truly looking for the root of the problem instead of symptoms, then you have to find out about the inner workings of the money system.
Root of the problem is being comfortable living (or operating) on credit, and even though it has tax benefits (in the US) it's interests (well, not with the new US interest rate) and risks should be enough to scare people.
A lot of the complexities are the results of the rules imposed on banks, though the banks do have lobbiest.
...). All of these things make different loan accounts different.
As far as mixing account types into one account -- you can usually mix savings and checking (AKA checking with interest) but there will be interest or higher minimum balance rules.
Many banks also offer various forms of overdraft protection, many of which are essentially a line of credit, though usually with a sharp penalty.
Lenders who lend someone else's money need to know how long they long they can use that money and depositers need to know how long they might have to wait to get their money back. That is why a 5 year CD has a greater interest rate than a 3 month CD. Banks make assumptions that checking account deposits must stay fairly liquid, savings account deposits semi-liquid, and CDs are solid until they mature (relative to the depositor of course)
Keeping buckets of money separate and labeled is good.
Lending is the flip side of that; knowing how long money is lent for is important to planning, meeting regulations, and covering transaction costs.
Their's also the rules about how a loan is repaid (lump sum, periodic payments,
Most cell providers allow you to send SMS from a websites (eg. vtext.com for Verizon) and on that you input the sending numbers, so if the actual sending numbers are used that is exactly no protection against anything except an idiot who uses his real number to wrongly try to remotely disable a laptop or DOS it.
Do you kiss your mother with that mouth?
It's a giant game of chicken between the ISPs. They all know that they can't individually block Google or their users would raise Hell and try to move to a different ISP, and ISPs that didn't block Google would win BIG.
What they are really trying to do is hide part of the expense of being an ISP from the client users (homes and small businesses) who can more easily change their ISP to content providers who would be forced to pay to reach the people.
If this happens you'll end up with nearly free Internet service in competitive locations, but the barrier for entry for content providers will become impossibly high.
Faster computation doesn't help communication-limited tasks very much . Faster communication doesn't help computation-limited tasks very much .
Or Clippy!
If I were a betting man I'd bet that much of what is being reported as living in a page file is likely also still in RAM, but that RAM is ready to be used either for something new or for it's current contents (mirror of what's in the page file).
It's likely that there's a bunch of stuff in each process that gets used very infrequently so the OS sees that it hasn't been changed in a while and goes ahead and puts it on the disk so that if/when that RAM is needed for something else the current contents will already be saved and no disk delay will be incurred in repurposing that RAM.
Reread the summary in Davros's voice, in creasing the volume and excitement as you get closer to the end. Come on -- it'll be fun.
Get off my lawn!
You might want to try replacing many programs as you can with busybox. It's versions of utilities are less complete than the standard gnu utilities, but they are all rolled into one binary, so most likely most of that binary will get cached in ram pretty early and stay there.
Also, for any packages you build you should try to use the -Os option for gcc, and perhaps even strip the binaries to remove unused symbols and debug info.
Building the system as though this was an embedded system with a small disk should be a win in most cases since fewer things have to go over the wire to load a file and more of the binaries can fit into cache.
Seriously. I've switched from Logitech to MS trackballs and keyboards, though Linux is my OS of choice.
What if you were to release said project under a FOSS license before the meeting where you are supposed to sign over the rights to it, and then inform the university's legal department of that and how it is now impossible to sign over the exclusive rights to your project to them?
Or get them to agree to a FOSS license?
That is unless you don't want it to be FOSS, but you could still sell a friend a license to it before signing over the rights. Of course you may end up being told "well you'll have to do another project that we do get the exclusive rights to". Go talk to a lawyer.
Tim O'Reilly seems to have made it work for him.
Didn't Rush have a song about this?
The way I understand it Dell will end up eating the loss, and the CC people will just with hold $1,700 from the next batch of money that goes to Dell.
I, like many of my peers, prefer my music on good old fashioned analog CDs.