text:
Saint Regis Mohawk Tribe Outraged at Senator McCaskill over Sovereign Immunity Bill
October 6, 2017, 12:16 PM 13
Senator Claire McCaskill (D-MO)
Yesterday, United States Senator Claire McCaskill (D-MO) introduced legislation that would strip Native American Indian Tribes of the ability to assert sovereign immunity in inter partes review (IPR) proceedings at the United States Patent and Trademark Office conducted by the Patent Trial and Appeal Board.
The hastily thrown together bill would only discriminate against Native American Indian Tribes and would allow state universities to continue to assert sovereign immunity pursuant to the PTAB's January 2017 decision relating to a patent owned by the University of Florida Research Foundation (UFRF). See UFRF's Win on 11th Amendment at the PTAB.
Also peculiar, to say the least, McCaskill's bill would only prevent Native American Indian Tribes from asserting sovereign immunity in IPR proceedings, but they could still assert sovereign immunity in post grant review (PGR) proceedings and covered business method (CBM) proceedings.
Why McCaskill would submit a bill that obviously discriminates against Native American Indian Tribes is unclear, although some are speculating that McCaskill, who is up for reelection in 2018, may become the champion of the patent infringer lobby in the coming months. Skeptical observers wonder whether this has to do with fundraising, which McCaskill has been separately Tweeting about recently. McCaskill has reportedly said she will need at least $30 million to mount a reelection campaign, and expects some $200 million to be spent by outside groups.
Meanwhile, McCaskill's seemingly calculated ploy to get out in front of other Senators, all alone in her demand for a legislative solution that strips Native American Indian Tribes of sovereign immunity, may backfire. The Saint Regis Mohawk Tribe, which acquired the Allergan RESTASIS® patents and then granted back to Allergan an exclusive license, issued a scathing statement, saying the Tribe is outraged that the legislation specifically targets Indian tribes while exempting state universities and other sovereign governments. The statement reads:
"The Saint Regis Mohawk Tribe is outraged that U.S. Senator Claire McCaskill (D-MO), has introduced legislation that specifically targets Indian tribes, yet exempts state universities and other sovereign governments engaged in the very same IPR process. The double standard that is being introduced by the Senator as a solution for a perceived abuse of the IPR proceedings does nothing to solve the underlying problem. The Tribes authority is inherent and has been reaffirmed through treaties and legislation from the earliest days of the country.
It is cruelly ironic that Indian Tribes, with the highest unmet health care needs in the entire country, are being attacked for exercising their sovereign obligation to fill gaps in health coverage caused by the federal government's abject failure to uphold its trust responsibility. The fact that the Mohawk community is home to three unmitigated EPA Superfund sites that harm the health of the community and surrounding non-Native communities is a stark example of the government's failure. Congress shouldn't double down on its mistakes by denying the Tribe's sovereign authority in the IPR process.
As the largest private employer in Northern New York, the Tribe has a responsibility to ensure the livelihood and well-being of its tribal members and its hundreds of non-Native employees. The Tribe remains committed to working with all Members of Congress to discuss how its recent economic diversification efforts benefits the Tribe, its members, and the surrounding communities without harming competition among pharmaceutical companies (both private and generic) or artificially inflating drug prices."
Meanwhile, headlines such as Sen. McCaskill unveils unprecedented bill to abrogate tribal sovereign immunity can already be found in Native American news outlets. Tribal governments all across the country are meeting to discuss this attack, which occurred without even a single hearing in the Senate.
Defenders of McCaskill's here on IPWatchdog.com have already made comments that can only be characterized as racist, which will only cause this ill-conceived and unforced error to blow even further out of control as that backwards mentality spreads.
"Creative avoidance of PTAB will continue to flourish as long as PTAB is permitted to discriminate against patent holders," Chris Gallagher commented. He is exactly right — that is what this is all about. Instead of discriminating against Native American Indians and stripping Tribes of sovereign immunity Senator McCaskill ought to look at the root problem, which is a PTAB that discriminates against patent owners and operates like a Kangaroo court. See Transgressions of the PTAB.
Gene Quinn Gene Quinn is a patent attorney and a leading commentator on patent law and innovation policy. Mr. Quinn has twice been named one of the top 50 most influential people [...see more]
13 comments so far.
"The hastily thrown together bill would only discriminate against Native American Indian Tribes and would allow state universities to continue to assert sovereign immunity"
Translation: "The bill would only waive sovereign immunity as to the entities whose sovereign immunity Congress has the constitutional authority to waive, but would not waive sovereign immunity where the XI amendment denies Congress the power to make such a waiver."
(oops – that last "non-partial" was an inadvertent typing)
Joachim,
"non-partial" is not to be confused with "secret."
And while "conspiracy" need not be ultra-secret, I am not certainly suggesting that the putative "conspiracy" is afoot.
As anyone with any access to a minimuem amount of "investigative" prowess could tell you, Google et al. has not been that "secretive" about either the number of trips or the amount of lobbying money that they have spent.
Exactly WHAT those trips discussed…
That's a different matter.
Non-partial
Joachim Martillo
I am not sure that Kangaroo Court implies secret direction. I have generally understood it as a court that jumps to conclusions on the basis of non-facts — a black defendant is guilty because all blacks are either criminals or potential criminals.
The phrase "star chamber" is more suggestive of conspiracy.
Pro Se
October 7, 2017 10:44 am
Oil States is case (1) and SAS is case (2).
The drama can't ever be higher for the future of patent health than this. I'll be on line at the Supreme Court this day.
Benny,
perhaps both…
Is this discrimination against Native American tribes, or is it equality with non "Native" Americans ?
Bluejay,
One can only hope….
Oil States ends the PTAB fraud.
Interesting comment Charles.
But I think that the designation of "kangaroo court" already implies that there is a non-partial actor to whom or for whom the court is beholding to.
Charles Barton
It is misdirection only to attack the PTAB as a kangaroo court. The PTAB acts at someone's behest. Programs like SAWS and Second Look don't come out of nowhere.
Identifying PTAB misbehavior doesn't hurt, but really the SEC and the FBI should be groveling through all the records of the USPTO because of some strong indications of the violation of the STOCK Act
The Time Is Now To Act
Hi Gene- I thought I would bring this organization to your attention; which has a DC office. They have litigation support as well as train Native Americans as attorneys.
Executive Director Echohawk (National Law Review Top 100 most influential) and K. Jerome Gottschalk are good contacts. Echohawk is reachable at their Boulder office number.
https://www.narf.org/about-us/staff/
Native Americans have historically voted on a Democratic party line basis. If this misguided nonsense from Democratic Senator McCaskill continues, emphasis in the preceding sentence on the word "historically."


text:
From Charlize To Cara, 6 Women Share Their Life Lessons With Dior
By Hannah Coates 21 September 2020
If you're in need of some encouragement today, you might just find it from the likes of Charlize Theron, Cara Delevingne and Paloma Elsesser, who are sharing the wisdom they've accumulated in their careers as part of Dior's new campaign, #DiorStandsWithWomen. The Parisian fashion house has released a series of short films (available on its YouTube channel), in which a number of accomplished women – from artists and actresses to scientists and models – recount their life journeys, the challenges they have faced, and the things they've learned along the way. Here, British Vogue shares an insight into their tales, and a glimpse of the gorgeous portraits that accompany them. Prepare to feel inspired.
Dior Puts Its Enchanting "Designer Of Dreams" Exhibition Online
By Alice Newbold
Charlize Theron, Actress
"My mom used to always say when I was a little girl, 'It is your duty as a human being to stand up for those who can't speak for themselves.'"
Paloma Elsesser, Model
"I definitely noticed at a young age [what] gender is supposed to look like, what bodies are supposed to look like, how we're supposed to speak, how quiet we should be, how little we should know... All of these very binary ideas of how we're supposed to exist. My work is centred in advocating for a spectrum of bodies… I can't represent for everyone, but my voice hopefully will carve space for more people to see themselves."
Cara Delevingne, Actress and Model
"When you look back in history, you know there have been so many incredible women who have come before us, who have paved the way to not have to be labelled, or be put in a box, or pigeonholed… To be able to be multifaceted, multilayered, [and] be unapologetic."
Li Bingbing, Actress
"I hope that more women can face themselves very truthfully and bravely, love themselves more, and have an exciting life and vitality."
Golshifteh Farahani, Actress
"As a woman, I don't defend women or men, I defend truthfulness. I defend the truth."
Parris Goebel, Dancer and Choreographer
"I feel history hasn't allowed us to shine as bright as we should, and I think our time is coming. We shouldn't wait for permission or validation to be able to love our bodies."
More from British Vogue:
Prepare To Want Erdem-esque Wind-Flushed Cheeks This Autumn
From Charlize Theron To Jessica Alba, Celebrities Are Finding Cool, Creative Ways To Make Us Vote
By Susan Devaney 30 October 2020

redpajama_set_name: RedPajamaCommonCrawl


Want to take on new and emerging markets all over the world? At Manchester Met, we'll help you master vital skills in international business strategy.
As well as ethical and global management, you'll also refine your expertise by exploring the political economy and how it can affect global trade.
You can tailor the course to concentrate on areas that you find most interesting. You'll choose two option units from a range of business specialisms such as international brand strategy, business psychology and entrepreneurship.
We'll also help you understand working practices from different territories and build the skills you need to effectively manage people from different cultures and backgrounds.
You'll look behind the scenes at global organisations during regular business visits, and see first-hand how they operate day-to-day.
You'll also have the opportunity to take an optional 36-48 week internship which will give you a unique insight into how international organisations work. This could be a real boost to your career, allowing you to add relevant, professional experience to your CV.
Taught by experts – you'll learn from academics with experience working for global businesses. They also carry out cutting-edge research in their fields which feeds into your learning.
A city of opportunities – with global organisations and innovative start-ups, Manchester offers a wealth of opportunities.Use our connections with employers to enhance your studies and professional network.
Unique insights – learn from guest lecturers who have experience working on an international scale. You'll get an insider's view of some of the world's most ambitious global businesses.
Customisable degree - specialise in the areas of international business that you're most interested in to help shape your future career.
Optional internship – gain extensive professional experience during an optional 36-48 week internship with an international business.
Live client briefs – refine your skills by working on projects with real clients. You'll gain important experience for the working world.
Valuable insights – see how businesses are structured through visits to global organisations such as Manchester United, LandRover Jaguar and BBC MediaCityUK.
Boost your employability – explore a wide range of management roles all over the world. The skills you develop on this course are relevant across international markets.
Visit the International Business Management - MSc page on the Manchester Metropolitan University website for more details!


text:
Buying a Car Guide
2004 Cadillac Seville
2004 Cadillac Seville Links
2004 Cadillac Seville - Specs
2004 Cadillac Seville - Photos
2004 Cadillac Reviews
2004 Cadillac Seville - Price Quote
Visit Cadillac for more information on the Cadillac Seville.
It's the end of an era for the Cadillac Seville. 2004 will be the last year the Seville is offered by Cadillac. In anticipation, Cadillac has already discontinued the Seville STS, retaining only the entry-level SLS to try and squeeze out a few more purchases from devoted Seville enthusiasts.
The Cadillac Seville will not depart meekly, however. Though there obviously aren't any major redesigns for the 2004 Cadillac Seville SLS, it is still at the forefront of comfort and style, just as it has always been. A luxury car with class, the Seville SLS will go out with its head held high.
The Seville SLS is the sole trim for 2004.
The four-door 2004 Cadillac Seville SLS is like other Cadillac sedans in that it offers impressive interior space. Five passengers fit easily on the inside.
Though interior equipment doesn't change from last year's model, that is not to say that the 2004 Cadillac Seville SLS is lacking in any sense. After all, it is a luxury vehicle. Air conditioning with dual zone automatic climate control, a power tilt/telescoping leather-wrapped steering wheel with radio and climate controls, leather upholstery, 10-way power front seats with power lumbar adjustment and driver-seat memory and heated front and rear seats are all standard.
Also standard is the convenient OnStar system with its safety and security features. Optional equipment includes a navigation system and a power sunroof, among others.
The 2003 Seville received a freshened exterior look featuring a body-colored grille. New colors for the new model year include Light Platinum and White Lightning.
Though the Cadillac Seville will make way for an all-new Sigma-architecture based 2005 STS performance sedan, it's hard to believe it could be for power reasons. With a 4.6-liter Northstar V8, the front-wheel drive Seville SLS can move quite well. The engine can generate 275 horsepower at 5600 rpm and 300 lb-ft of torque at 4000 rpm.
4-speed electronic automatic with overdrive and viscous-type converter clutch continues to be the transmission of choice for the Seville SLS.
Also returning for 2004 are the StabiliTrak system and full-range traction control. With Magnasteer variable assist speed-sensitive steering and these two systems, the result is supreme handling ability.
The 2004 Cadillac Seville SLS will go out a safe sedan. It has antilock 4-wheel disc brakes, dual front airbags, front side airbags, a rear-obstacle detection system, wiper-activated headlights, cornering lights and fog lights.
2004 Cadillac Seville - New for 2004
STS model ends production
New colors: Light Platinum and White Lightening
Competing Model Reviews
04 Acura RL
04 Chrysler 300M
04 Volvo S80
Other 2004 Cadillac Reviews
2004 Cadillac XLR
Other Cadillac Seville Reviews


One among the most frequent electrical wiring concerns is on how to wire a swap. Though using switches at your house is quite simple, wiring one particular may well not be that quick for everybody. An ON-OFF switch is definitely quite simple to wire. You'll find different kinds of switches, but for this example, let's say you will be putting in a single-pole toggle switch, a very prevalent change (plus the most straightforward).
You'll find 3 colours of wires in a very common single-pole toggle switch: black, white, and green. Splice the black wire in two and link them over the terminal screws - just one on top rated as well as other within the base screw from the change. The white wire serves for a resource of uninterrupted ability and is normally linked into a light-weight coloured terminal screw (e.g., silver). Connect the green wire towards the ground screw of your respective swap.
These ways would usually be adequate to help make a normal change perform with no trouble. Nonetheless, in the event you are usually not self-assured that you simply can execute the endeavor correctly and securely you superior allow the pros do it alternatively. Following all, you will find a cause why this endeavor is one of the most typical electrical wiring concerns requested by many people.
For a few cause, how you can wire a ceiling fan can also be one among quite possibly the most popular electrical wiring inquiries. To simplify this job, you need to use just one change to get a single ceiling fan. To wire the admirer, it's simply a matter of connecting the black wire of your ceiling fan for the black wire in the change. When there is a light, the blue wire must be linked for the black wire on the swap at the same time.
There are reasons why these are one of the most typically questioned electrical wiring thoughts. A person, numerous feel it really is simple to carry out, and two, these are definitely the frequent electrical tasks in your house. But then you must not set your security at risk in the goal to economize. The stakes could even be significantly greater for those who seek to save money and do an electrical wiring work without having sufficient understanding or knowledge.


2 Mar 2018 Washington, D.C.
Illegal alien activists shielded from deportation by the President Obama-created Deferred Action for Childhood Arrivals (DACA) program and Democrats are blaming each other for unsuccessfully passing an amnesty.
Last month, the open borders lobby, illegal alien activists, and Democrats failed to coalesce behind a number of amnesty plans for DACA illegal aliens that would have, at the same time, offset the amnesty with a reduction in legal immigration to benefit America's working and middle class.
Now, the two groups — the activists and Democrats — are blaming each other for the failed effort that is expected to result in DACA illegal aliens eventually being deported out of the United States.
In a report by Roll Call, Democrat aides blast illegal alien activists for going after Democrat members of Congress, such as when crowds of open borders activists stormed the New York City home of Senate Minority Chuck Schumer.
Likewise, Democrats turned on their illegal alien allies for going after liberals in Congress for not keeping the government shut down until an amnesty was passed.
At the same time, open borders activists continued blaming Democrats in Congress for not doing enough to pass a large-scale amnesty that would have come at the expense of America's working and middle class.
DACA illegal aliens, last month, stormed the offices of multiple congressmen and Senators, demanding that they pass an immediate amnesty that all 12 to 30 million illegal aliens living in the U.S. are entitled to.
When Democrats failed to keep the government shut down for amnesty in January, DACA illegal aliens immediately took to the U.S. Capitol to hold a mock funeral, as Breitbart News reported.
The group of activists stood around in a circle as each illegal alien came forward saying they "deserve" and are entitled to an amnesty, each dropping an orange flower on the ground in a mock funeral-style event.
Here we are in the Senate Rotounda.
We are setting flowers for the dreams killed and for our community that has to wait even longer til they get protections.
This is in you Congress.
For example, a DACA amnesty would put more citizen children of illegal aliens — known as "anchor babies" — on federal welfare, as Breitbart News reported, while American taxpayers would be potentially left with a $26 billion bill.


Copyright © 2010 Red Hat Inc. and others.
This document explains how to manage power consumption on Fedora 14 systems effectively. The following sections discuss different techniques that lower power consumption (for both server and laptop), and how each technique affects the overall performance of your system. Please note: This document is still under development, is subject to heavy change, and is provided here as a preview. The content and instructions contained within should not be considered complete, and should be used with caution.
If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: http://bugzilla.redhat.com/bugzilla/ against the product Fedora Documentation.
Limiting the power used by computer systems is one of the most important aspects of green IT (environmentally friendly computing), a set of considerations that also encompasses the use of recyclable materials, the environmental impact of hardware production, and environmental awareness in the design and deployment of systems. In this document, we provide guidance and information regarding power management of your systems running Fedora 14.
At the core of power management is an understanding of how to effectively optimize energy consumption of each system component. This entails studying the different tasks that your system performs, and configuring each component to ensure that its performance is just right for the job.
As a rule, lowering the power consumption of a specific component (or of the system as a whole) will lead to lower heat and naturally, performance. As such, you should thoroughly study and test the decrease in performance afforded by any configurations you make, especially for mission-critical systems.
By studying the different tasks that your system performs, and configuring each component to ensure that its performance is just sufficient for the job, you can save energy, generate less heat, and optimize battery life for laptops. Many of the principles for analysis and tuning of a system in regard to power consumption are similar to those for performance tuning. To some degree, power management and performance tuning are opposite approaches to system configuration, because systems are usually optimized either towards performance or power. This manual describes the tools that the Fedora Project provides and the techniques we have developed to help you in this process.
Fedora 14 already comes with a lot of new power management features that are enabled by default. They were all selectively chosen to not impact the performance of a typical server or desktop use case. However, for very specific use cases where maximum throughput, lowest latency, or highest CPU performance is absolutely required, a review of those defaults might be necessary.
Q: How much do I need to optimize?
Q: Will optimization reduce system performance to an unacceptable level?
Q: Will the time and resources spent to optimize the system outweigh the gains achieved?
The importance of power optimization depends on whether your company has guidelines that need to be followed or if there are any regulations that you have to fulfill.
How much do I need to optimize?
Several of the techniques we present do not require you to go through the whole process of auditing and analyzing your machine in detail but instead offer a set of general optimizations that typically improve power usage. Those will of course typically not be as good as a manually audited and optimized system, but provide a good compromise.
Will optimization reduce system performance to an unacceptable level?
Most of the techniques described in this document impact the performance of your system noticeably. If you choose to implement power management beyond the defaults already in place in Fedora 14, you should monitor the performance of the system after power optimization and decide if the performance loss is acceptable.
Will the time and resources spent to optimize the system outweigh the gains achieved?
Optimizing a single system manually following the whole process is typically not worth it as the time and cost spent doing so is far higher than the typical benefit you would get over the lifetime of a single machine. On the other hand if you for example roll out 10000 desktop systems to your offices all using the same configuration and setup then creating one optimized setup and applying that to all 10000 machines is most likely a good idea.
The following sections will explain how optimal hardware performance benefits your system in terms of energy consumption.
The kernel used in releases of Fedora prior to Fedora 8 used a periodic timer for each CPU. This timer prevents the CPU from truly going idle, as it requires the CPU to process each timer event (which would happen every few milliseconds, depending on the setting), regardless of whether any process was running or not. A large part of effective power management involves reducing the frequency at which CPU wakeups are made.
Because of this, the Linux kernel in Fedora 14 eliminates the periodic timer: as a result, the idle state of a CPU is now tickless. This prevents the CPU from consuming unnecessary power when it is idle. However, benefits from this feature can be offset if your system has applications that create unnecessary timer events. Polling events (such as checks for volume changes, mouse movement, and the like) are examples of such events.
Fedora 14 includes tools with which you can identify and audit applications on the basis of their CPU usage. Refer to Chapter 2, Power management auditing and analysis for details.
If your hardware has support for these features and they are enabled in the BIOS, Fedora 14 will use them by default.
As obvious as this might sound, one of the best ways to actually save power is to turn off systems. For example, your company can develop a corporate culture focused on "green IT" awareness with a guideline to turn of machines during lunch break or when going home. You also might consolidate several physical servers into one bigger server and virtualize them using the virtualization technology we ship with Fedora 14.
The detailed manual audit, analysis, and tuning of a single system is usually the exception because the time and cost spent to do so typically outweighs the benefits gained from these last pieces of system tuning. However, performing these tasks once for a large number of nearly identical systems where you can reuse the same settings for all systems can be very useful. For example, consider the deployment of thousands of desktop systems, or a HPC cluster where the machines are nearly identical. Another reason to do auditing and analysis is to provide a basis for comparison against which you can identify regressions or changes in system behavior in the future. The results of this analysis can be very helpful in cases where hardware, BIOS, or software updates happen regularly and you want to avoid any surprises with regard to power consumption. Generally, a thorough audit and analysis gives you a much better idea of what is really happening on a particular system.
Auditing and analyzing a system with regard to power consumption is relatively hard, even with the most modern systems available. Most systems do not provide the necessary means to measure power use via software. Exceptions exist though: the ILO management console of Hewlett Packard server systems has a power management module that you can access through the web. IBM provides a similar solution in their BladeCenter power management module. On some Dell systems, the IT Assistant offers power monitoring capabilities as well. Other vendors are likely to offer similar capabilities for their server platforms, but as can be seen there is no single solution available that is supported by all vendors. If your system has no inbuilt mechanism to measure power consumption, a few other choices exist. You could install a special power supply for your system that offers power consumption information through USB. The Gigabyte Odin GT 550 W PC power supply is one such example, and software to read out those values under Linux is available externally from http://mgmt.sth.sze.hu/~andras/dev/gopsu/. As a last resort, some external watt meters like the Watts up? PRO have a USB connector.
Direct measurements of power consumption is often only necessary to maximize savings as far as possible. Fortunately, other means are available to measure if changes are in effect or how the system is behaving. This chapter describes the necessary tools.
The tickless kernel in Fedora allows the CPU to enter the idle state more frequently, reducing power consumption and improving power management. The new PowerTOP tool identifies specific components of kernel and userspace applications that frequently wake up the CPU. PowerTOP was used in development to perform the audits described in Section 3.11, "Optimizations in User Space" that led to many applications being tuned in this release, reducing unnecessary CPU wake up by a factor of ten.
Note that you will need to run PowerTOP with root privileges to allow the application to do anything useful.
When it runs, PowerTOP gathers statistics from the system and presents you with a list of the components that are sending wakeups to the CPU most frequently. PowerTOP also makes suggestions for tuning the system for lower power consumption. These suggestions appear at the bottom of the screen, and specify a key for you to press to accept PowerTOP's suggestion. As PowerTOP refreshes periodically, further suggestions appear. In Figure 2.1, "PowerTOP in Operation", note the suggestion to increase the VM dirty writeback time, and the key (W) to press to accept the suggestion.
When it runs, PowerTOP gathers statistics from the system and presents you with several important lists of information. At the top is a list of how long your CPU cores have been in each of the available C and P states. The longer the CPU stays in the higher C or P stats the better (C4 being higher than C3) and is a good indicator of how well the system is tuned towards CPU utilization. Your goal should be residency of 90% or more in the highest C or P state while the system is idle.
The second piece of information is a summary of the actual wakeups per second of the machine. The number of wakeups per second gives you a good measure of how well the services or the devices and drivers of the kernel are performing with regard to power usage on your system. The more wakeups per second you have, the more power is consumed, so lower is better here.
Next, PowerTOP provides an estimate of the actual power usage of the system, if available. Expect PowerTOP to report this figure on laptops while they are in battery mode.
If the trace looks like it is repeating itself, then you probably have found a busy loop. To fix this would require a code change in that component and that again goes beyond the scope of this document.
Finally, PowerTOP also makes suggestions for tuning the system for lower power consumption. These suggestions appear at the bottom of the screen, and specify a key for you to press to accept PowerTOP's suggestion. As PowerTOP refreshes periodically, further suggestions appear. In Figure 2.1, "PowerTOP in Operation", note the suggestion to increase the VM dirty writeback time, and the key (W) to press to accept the suggestion. These changes will only be active until the next reboot. To help you make the changes permanent, PowerTOP displays the exact command it runs to perform this optimization. Add the command to your /etc/rc.local file with your preferred text editor so that it takes effect every time that the computer starts.
The Less Watts website publishes a list of applications that PowerTOP has identified as keeping CPUs active. Refer to http://www.lesswatts.org/projects/powertop/known.php.
Diskdevstat and netdevstat are SystemTap tools that collect detailed information about the disk activity and network activity of all applications running on a system. These tools were inspired by PowerTOP, which shows the number of CPU wakeups by every application per second (refer to Section 2.2, "PowerTOP"). The statistics that these tools collect allow you to identify applications that waste power with many small I/O operations rather than fewer, larger operations. Other monitoring tools that measure only transfer speeds do not help to identify this type of usage.
Flag whether to histogram for all the collected data at the end of the run.
These three applications have a WRITE_CNT greater than 0, which means that they performed some form of write during the measurement. Of those, plasma was the worst offender by a large degree: it performed the most write operations, and of course the average time between writes was the lowest. Plasma would therefore be the best candidate to investigate if you were concerned about power-inefficient applications.
In this example, the output of the strace contained a repeating pattern every 45 seconds that opened the KDE icon cache file of the user for writing followed by an immediate close of the file again. This led to a necessary physical write to the hard disk as the file metadata (specifically, the modification time) had changed. The final fix was to prevent those unnecessary calls when no updates to the icons had occurred.
The Battery Life Tool Kit (BLTK), is a test suite that simulates and analyzes battery life and performance. BLTK achieves this by performing sets of tasks that simulate specific user groups and reporting on the results. Although developed specifically to test notebook performance, BLTK can also report on the performance of desktop computers when started with the -a.
BLTK allows you to generate very reproducible workloads that are comparable to real use of a machine. For example, the office workload writes a text, corrects things in it, and does the same for a spreadsheet. Running BLTK combined with PowerTOP or any of the other auditing or analysis tool allows you to test if the optimizations you performed have an effect when the machine is actively in use instead of only idling. Because you can run the exact same workload multiple times for different settings, you can compare results for different settings.
BLTK supports a large number of more specialized options. For details, refer to the bltk man page.
Tuned is a daemon that monitors the use of system components and dynamically tunes system settings based on that monitoring information. Dynamic tuning accounts for the way that various system components are used differently throughout the uptime for any given system. For example, the hard drive is used heavily during startup and login, but is barely used later when a user might mainly work with applications like OpenOffice or email clients. Similarly, the CPU and network devices are used differently at different times. Tuned monitors the activity of these components and reacts to changes in their use.
As a practical example, consider a typical office workstation. Most of the time, the Ethernet network interface will be very inactive. Only a few emails will go in and out every once in a while or some web pages might be loaded. For those kinds of loads, the network interface doesn't have to run at full speed all the time, as it does by default. Tuned has a monitoring and tuning plugin for network devices that can detect that low activity and then automatically lower the speed of that interface, typically resulting in lower power usage. If activity on the interface increases drastically for a longer period of time, for example because a DVD image is being downloaded or an email with a large attachment is opened, tuned detects this and sets the interface speed to maximum to offer the best performance while the activity level is so high. This principle is used for the other plugins for CPU and hard disks as well.
Network devices are not configured to behave this way by default because speed changes can take several seconds to take effect and therefore directly and visibly impact the user experience. Similar considerations apply for the CPU and hard drive tuning plugins. When a hard drive has been spun down, it can take several seconds for it to spin up again which results in an observed lack of responsiveness of the system during that period. The latency side effect is smallest for the CPU plugin, but it is still at least measurable, though hardly noticeable by a user.
Alongside of tuned we now also offer ktune. Ktune was originally a framework and service to optimize the performance of a machine for a specific use cases. Since then, ktune has improved to such a degree that we now use it as the static part of our general tuning framework. It is mainly used in the different predefined profiles described in Section 2.5.2, "Tuned-adm".
Installing the tuned package also sets up a sample configuration file at /etc/tuned.conf and activates the default profile.
start tuned as a daemon instead of in the foreground.
use a configuration file with the specified name and path, for example, --conffile=/etc/tuned2.conf. The default is /etc/tuned.conf.
use the highest level of logging.
The tuned.conf file contains configuration settings for tuned. By default, it is located at /etc/tuned.conf, but you can specify a different name and location by starting tuned with the --conffile option.
The config file must always contain a [main] section that defines the general parameters for tuned. The file then contains a section for each plugin.
the interval at which tuned should monitor and tune the system, in seconds. The default value is 10.
specifies whether output should be verbose. The default value is False.
specifies the minimum priority of messages to be logged. In descending order, allowable values are: critical, error, warning, info, and debug. The default value is info.
specifies the maximum priority of messages to be logged; any messages with this priority or lower will not be logged. In descending order, allowable values are: critical, error, warning, info, and debug. The value notset disables this option.
specifies whether the plugin is enabled or not. The default value is True.
specifies whether output should be verbose. If not set for this plugin, the value is inherited from [main].
specifies the minimum priority of messages to be logged. If not set for this plugin, the value is inherited from [main].
Often, a detailed audit and analysis of a system can be very time consuming and might not be worth the few extra watts you might be able to save by doing so. Previously, the only alternative was simply to use the defaults. Therefore, Fedora 14 includes separate profiles for specific use cases as an alternative between those two extremes, together with the tuned-adm tool that allows you to switch between these profiles easily at the command line. Fedora 14 includes a number of predefined profiles for typical use cases that you can simply select and activate with the tuned-adm command, but you can also create, modify or delete profiles yourself.
the default power-saving profile. It has the lowest impact on power saving of the available profiles and only enables CPU and disk plugins of tuned.
a power-saving profile directed at desktop systems. Enables ALPM power saving for SATA host adapters (refer to Section 3.6, "Aggressive Link Power Management") as well as the CPU, Ethernet, and disk plugins of tuned.
a power-saving profile directed at server systems. Enables ALPM powersaving for SATA host adapters, disables CD-ROM polling through HAL (refer to the hal-disable-polling man page) and activates the CPU and disk plugins of tuned.
a medium-impact power-saving profile directed at laptops running on AC. Enables ALPM powersaving for SATA host adapters, WiFi power saving, as well as the CPU, Ethernet and disk plugins of tuned.
a high-impact power-saving profile directed at laptops running on battery. It activates all power saving mechanisms from the previous profiles plus it enables the multi-core power-savings scheduler for low wakeup systems and makes sure that the ondemand governor is active and that AC97 audio power-saving is enabled. You can use this profile to save the maximum amount of power on any kind of system, not only laptops on battery power. The tradeoff for this profile is a noticeable impact on performance, specifically latency of disk and network I/O.
a server profile for typical throughput performance tuning. It disables tuned and ktune power saving mechanisms, enables sysctl settings that improve the throughput performance of your disk and network I/O, and switches to the deadline scheduler.
a server profile for typical latency performance tuning. it disables tuned and ktune power saving mechanisms and enables sysctl settings that improve the latency performance of your network I/O.
the configuration for the tuned service to be active for this profile.
the sysctl settings used by ktune. The format is identical to the /etc/sysconfig/sysctl file (refer to the sysctl and sysctl.conf man pages).
the configuration file of ktune itself, typically /etc/sysconfig/ktune.
an init-style shell script used by the ktune service which can run specific commands during system startup to tune the system.
In Fedora 11 DeviceKit-power assumed the power management functions that were part of HAL and some of the functions that were part of GNOME Power Manager in previous releases of Fedora (refer also to Section 2.7, "GNOME Power Manager". In Fedora 13, DeviceKit-power was renamed to UPower. UPower provides a daemon, an API, and a set of command-line tools. Each power source on the system is represented as a device, whether it is a physical device or not. For example, a laptop battery and an AC power source are both represented as devices.
displays the parameters for all power devices on the system.
displays the CPU wakeups on the system.
monitors the system for changes to power devices, for example, the connection or disconnection of a source of AC power, or the depletion of a battery. Press Ctrl+C to stop monitoring the system.
monitors the system for changes to power devices, for example, the connection or disconnection of a source of AC power, or the depletion of a battery. The --monitor-detail option presents more detail than the --monitor option. Press Ctrl+C to stop monitoring the system.
GNOME Power Manager is a daemon that is installed as part of the GNOME desktop. Much of the power-management functionality that GNOME Power Manager provided in early releases of Fedora became part of DeviceKit-power in Fedora 11, renamed to UPower in Fedora 13 (refer to Section 2.6, "UPower". However, GNOME Power Manager remains a front end for that functionality. Through an applet in the system tray, GNOME Power Manager notifies you of changes in your system's power status; for example, a change from battery to AC power. It also reports battery status, and warns you when battery power is low.
Use the On AC Power and On Battery Power tabs to specify how much time must pass before the display is turned off on an inactive system, how much time must pass before an inactive system is put to sleep, and whether the system should spin down hard disks when not in use. The On Battery Power tab also allows you to set the display brightness and to choose a behavior for a system with a critically low battery. For example, by default, GNOME Power Manager makes a system hibernate when its battery level reaches a critically low level. Use the General tab to set behaviours for the (physical) power button and suspend button on your system, and to specify the circumstances under which the GNOME Power Manager icon should appear in the system tray.
vmstat gives you detailed information about processes, memory, paging, block I/O, traps, and CPU activity. Use it to take a closer look at what the system overall does and where it is busy.
iostat is similar to vmstat, but only for I/O on block devices. It also provides more verbose output and statistics.
blktrace is a very detailed block I/O trace program. It breaks down information to single blocks associated with applications. It is very useful in combination with diskdevstat.
the operating or running state. In this state, the CPU is working and not idle at all.
a state where the processor is not executing any instructions but is typically not in a lower power state. The CPU can continue processing with practically no delay. All processors offering C-States need to support this state. Pentium 4 processors support an enhanced C1 state called C1E that actually is a state for lower power consumption.
a state where the the clock is frozen for this processor but it keeps the complete state for its registers and caches, so after starting the clock again it can immediately start processing again. This is an optional state.
a state where the processor really goes to sleep and doesn't need to keep it's cache up to date. Waking up from this state takes considerably longer than from C2 due to this. Again this is an optional state.
Recent Intel CPUs with the "Nehalem" microarchitecture feature a new C-State, C6, which can reduce the voltage supply of a CPU to zero, but typically reduces power consumption by between 80% and 90%. The kernel in Fedora 14 includes optimizations for this new C-State.
One of the most effective ways to reduce power consumption and heat output on your system is to use CPUfreq. CPUfreq — also referred to as CPU speed scaling — allows the clock speed of the processor to be adjusted on the fly. This enables the system to run at a reduced clock speed to save power. The rules for shifting frequencies, whether to a faster or slower clock speed, and when to shift frequencies, are defined by the CPUfreq governor.
The governor defines the power characteristics of the system CPU, which in turn affects CPU performance. Each governor has its own unique behavior, purpose, and suitability in terms of workload. This section describes how to choose and configure a CPUfreq governor, the characteristics of each governor, and what kind of workload each governor is suitable for.
The following sections explain how optimal hardware performance benefits your system in terms of energy consumption.
This section lists and describes the different types of CPUfreq governors available in Fedora 14.
The Performance governor forces the CPU to use the highest possible clock frequency. This frequency will be statically set, and will not change. As such, this particular governor offers no power saving benefit. It is only suitable for hours of heavy workload, and even then only during times wherein the CPU is rarely (or never) idle.
By contrast, the Powersave governor forces the CPU to use the lowest possible clock frequency. This frequency will be statically set, and will not change. As such, this particular governor offers maximum power savings, but at the cost of the lowest CPU performance.
The term "powersave" can sometimes be deceiving, though, since (in principle) a slow CPU on full load consumes more power than a fast CPU that is not loaded. As such, while it may be advisable to set the CPU to use the Powersave governor during times of expected low activity, any unexpected high loads during that time can cause the system to actually consume more power.
The Powersave governor is, in simple terms, more of a "speed limiter" for the CPU than a "power saver". It is most useful in systems and environments where overheating can be a problem.
The Ondemand governor is a dynamic governor that allows the CPU to achieve maximum clock frequency when system load is high, and also minimum clock frequency when the system is idle. While this allows the system to adjust power consumption accordingly with respect to system load, it does so at the expense of latency between frequency switching. As such, latency can offset any performance/power saving benefits offered by the Ondemand governor if the system switches between idle and heavy workloads too often.
For most systems, the Ondemand governor can provide the best compromise between heat emission, power consumption, performance, and manageability. When the system is only busy at specific times of the day, the Ondemand governor will automatically switch between maximum and minimum frequency depending on the load without any further intervention.
The Userspace governor allows userspace programs (or any process running as root) to set the frequency. This governor is normally used in conjunction with the cpuspeed daemon. Of all the governors, Userspace is the most customizable; and depending on how it is configured, it can offer the best balance between performance and consumption for your system.
Like the Ondemand governor, the Conservative governor also adjusts the clock frequency according to usage (like the Ondemand governor). However, while the Ondemand governor does so in a more aggressive manner (that is from maximum to minimum and back), the Conservative governor switches between frequencies more gradually.
This means that the Conservative governor will adjust to a clock frequency that it deems fitting for the load, rather than simply choosing between maximum and minimum. While this can possibly provide significant savings in power consumption, it does so at an ever greater latency than the Ondemand governor.
You can enable a governor using cron jobs. This allows you to automatically set specific governors during specific times of the day. As such, you can specify a low-frequency governor during idle times (for example after work hours) and return to a higher-frequency governor during hours of heavy workload.
For instructions on how to enable a specific governor, refer to Procedure 3.2, "Enabling a CPUfreq Governor" in Section 3.2.2, "CPUfreq Setup".
Before selecting and configuring a CPUfreq governor, you need to add the appropriate CPUfreq driver first.
Use modprobe to add the appropriate CPUfreq driver.
When using the above command, be sure to remove the .ko filename suffix.
When choosing an appropriate CPUfreq driver, always choose acpi-cpufreq over p4-clockmod. While using the p4-clockmod driver reduces the clock frequency of a CPU, it does not reduce the voltage. acpi-cpufreq, on the other hand, reduces voltage along with CPU clock frequency, allowing less power consumption and heat output for each unit reduction in performance.
Some CPUfreq governors may not be available for you to use. In this case, use modprobe to add the necessary kernel modules that enable the specific CPUfreq governor you wish to use. These kernel modules are available in /lib/modules/[kernel version]/kernel/drivers/cpufreq/.
cpuinfo_min_freq — Shows the CPU's available minimum operating frequency (in KHz).
cpuinfo_max_freq — Shows the CPU's available maximum operating frequency (in KHz).
scaling_driver — Shows what CPUfreq driver is used to set the frequency on this CPU.
scaling_available_governors — Shows the CPUfreq governors available in this kernel. If you wish to use a CPUfreq governor that is not listed in this file, refer to Procedure 3.2, "Enabling a CPUfreq Governor" in Section 3.2.2, "CPUfreq Setup" for instructions on how to do so.
scaling_governor — Shows what CPUfreq governor is currently in use. To use a different governor, simply use echo [governor] > /sys/devices/system/cpu/[cpu ID]/cpufreq/scaling_governor (refer to Procedure 3.2, "Enabling a CPUfreq Governor" in Section 3.2.2, "CPUfreq Setup" for more information).
cpuinfo_cur_freq — Shows the current speed of the CPU (in KHz).
scaling_available_frequencies — Lists available frequencies for the CPU, in KHz.
scaling_min_freq and scaling_max_freq — Sets the policy limits of the CPU, in KHz.
When setting policy limits, you should set scaling_max_freq before scaling_min_freq.
affected_cpus — Lists CPUs that require frequency coordination software.
scaling_setspeed — Used to change the clock speed of the CPU, in KHz. You can only set a speed within the policy limits of the CPU (as per scaling_min_freq and scaling_max_freq).
When a system is suspended, the kernel calls on drivers to store their states and then unloads them. When the system is resumed, it reloads these drivers, which attempt to reprogram their devices. The drivers' ability to accomplish this task determines whether the system can be resumed successfully.
Video drivers are particularly problematic in this regard, because the Advanced Configuration and Power Interface (ACPI) specification does not require system firmware to be able to reprogram video hardware. Therefore, unless video drivers are able to program hardware from a completely uninitialized state, they may prevent the system from resuming.
Fedora 14 includes greater support for new graphics chipsets, which ensures that suspend and resume will work on a greater number of platforms. In particular, support for NVIDIA chipsets has been greatly improved; in particular for the GeForce 8800 series.
Previously, the Linux kernel periodically interrupted each CPU on a system at a predetermined frequency — 100 Hz, 250 Hz, or 1000 Hz, depending on the platform. The kernel queried the CPU about the processes that it was executing, and used the results for process accounting and load balancing. Known as the timer tick, the kernel performed this interrupt regardless of the power state of the CPU. Therefore, even an idle CPU was responding to up to 1000 of these requests every second. On systems that implemented power saving measures for idle CPUs, the timer tick prevented the CPU from remaining idle long enough for the system to benefit from these power savings.
The kernel in Fedora 14 runs tickless: that is, it replaces the old periodic timer interrupts with on-demand interrupts. Therefore, idle CPUs are allowed to remain idle until a new task is queued for processing, and CPUs that have entered lower power states can remain in these states longer.
Active-State Power Management (ASPM) saves power in the Peripheral Component Interconnect Express (PCI Express or PCIe) subsystem by setting a lower power state for PCIe links when the devices to which they connect are not in use. ASPM controls the power state at both ends of the link, and saves power in the link even when the device at the end of the link is in a fully powered-on state.
sets PCIe link power states according to the defaults specified by the firmware on the system (for example, BIOS). This is the default state for ASPM.
sets ASPM to save power wherever possible, regardless of the cost to performance.
disables ASPM to allow PCIe links to operate with maximum performance.
ASPM policies are set in /sys/module/pcie_aspm/parameters/policy, but can also be specified at boot time with the pcie_aspm kernel parameter, where pcie_aspm=off disables ASPM and pcie_aspm=force enables ASPM, even on devices that do not support ASPM.
If pcie_aspm=force is set, hardware that does not support ASPM can cause the system to stop responding. Before setting pcie_aspm=force, ensure that all PCIe hardware on the system supports ASPM.
Aggressive Link Power Management (ALPM) is a power-saving technique that helps the disk save power by setting a SATA link to the disk to a low-power setting during idle time (that is when there is no I/O). ALPM automatically sets the SATA link back to an active power state once I/O requests are queued to that link.
Power savings introduced by ALPM come at the expense of disk latency. As such, you should only use ALPM if you expect the system to experience long periods of idle I/O time.
ALPM is only available on SATA controllers that use the Advanced Host Controller Interface (AHCI). For more information about AHCI, refer to http://www.intel.com/technology/serialata/ahci.htm.
This mode sets the link to its lowest power state (SLUMBER) when there is no I/O on the disk. This mode is useful for times when an extended period of idle time is expected.
This mode sets the link to the second lowest power state (PARTIAL) when there is no I/O on the disk. This mode is designed to allow transitions in link power states (for example during times of intermittent heavy I/O and idle I/O) with as small impact on performance as possible.
medium_power mode allows the link to transition between PARTIAL and fully-powered (that is "ACTIVE") states, depending on the load. Note that it is not possible to transition a link directly from PARTIAL to SLUMBER and back; in this case, either power state cannot transition to the other without transitioning through the ACTIVE state first.
ALPM is disabled; the link does not enter any low-power state when there is no I/O on the disk.
To check whether your SATA host adapters actually support ALPM you can check if the file /sys/class/scsi_host/host*/link_power_management_policy exists. To change the settings simply write the values described in this section to these files or display the files to check for the current setting.
Setting ALPM to min_power or medium_power will automatically disable the "Hot Plug" feature.
The POSIX standard requires that operating systems maintain file system metadata that records when each file was last accessed. This timestamp is called atime, and maintaining it requires a constant series of write operations to storage. These writes keep storage devices and their links busy and powered up. Since few applications make use of the atime data, this storage device activity wastes power. Significantly, the write to storage would occur even if the file was not read from storage, but from cache. For some time, the Linux kernel has supported a noatime option for mount and would not write atime data to file systems mounted with this option. However, simply turning off this feature is problematic because some applications rely on atime data and will fail if it is not available.
The kernel used in Fedora 14 supports another alternative — relatime. Relatime maintains atime data, but not for each time that a file is accessed. With this option enabled, atime data is written to the disk only if the file has been modified since the atime data was last updated (mtime), or if the file was last accessed more than a certain length of time ago (by default, one day).
By default, all filesystems are now mounted with relatime enabled. To suppress this feature across an entire system, use the boot parameter default_relatime=0. If relatime is enabled on a system by default, you can suppress it for any particular file system by mounting that file system with the option norelatime. Finally, to vary the default length of time before which the system will update a file's atime data, use the relatime_interval= boot parameter, specifying the period in seconds. The default value is 86400.
Fedora 14 supports the power capping features found in recent hardware, such as HP Dynamic Power Capping (DPC), and Intel Node Manager (NM) technology. Power capping allows administrators to limit the power consumed by servers, but it also allows managers to plan data centers more efficiently, because the risk of overloading existing power supplies is greatly diminished. Managers can place more servers within the same physical footprint and have confidence that if server power consumption is capped, the demand for power during heavy load will not exceed the power available.
Dynamic Power Capping is a feature available on select ProLiant and BladeSystem servers that allows system administrators to cap the power consumption of a server or a group of servers. The cap is a definitive limit that the server will not exceed, regardless of its current workload. The cap has no effect until the server reaches its power consumption limit. At that point, a management processor adjusts CPU P-states and clock throttling to limit the power consumed.
Dynamic Power Capping modifies CPU behavior independently of the operating system, however, HP's integrated Lights-Out 2 (iLO2) firmware allows operating systems access to the management processor and therefore applications in user space can query the management processor. The kernel used in Fedora 14 includes a driver for HP iLO and iLO2 firmware, which allows programs to query management processors at /dev/hpilo/dXccbN. The kernel also includes an extension of the hwmon sysfs interface to support power capping features, and a hwmon driver for ACPI 4.0 power meters that use the sysfs interface. Together, these features allow the operating system and user-space tools to read the value configured for the power cap, together with the current power usage of the system.
For further details, refer to the official site: HP Dynamic Power Capping.
Intel Node Manager imposes a power cap on systems, using processor P-states and T-states to limit CPU performance and therefore power consumption. By setting a power management policy, administrators can configure systems to consume less power during times when system loads are low, for example, at night or on weekends.
Intel Node Manager adjusts CPU performance using Operating System-directed configuration and Power Management (OSPM) through the standard Advanced Configuration and Power Interface. When Intel Node Manager notifies the OSPM driver of changes to T-states, the driver makes corresponding changes to processor P-states. Similarly, when Intel Node Manager notifies the OSPM driver of changes to P-states, the driver changes T-states accordingly. These changes happen automatically and require no further input from the operating system. Administrators configure and monitor Intel Node Manager with Intel Data Center Manager (DCM) software.
Fedora 14 saves power on graphics and display devices by eliminating several sources of unnecessary consumption.
Low-voltage differential signaling (LVDS) is an system for carrying electronic signals over copper wire. One significant application of the system is to transmit pixel information to liquid crystal display (LCD) screens in notebook computers. All displays have a refresh rate — the rate at which they receive fresh data from a graphics controller and redraw the image on the screen. Typically, the screen receives fresh data sixty times per second (a frequency of 60 Hz). When a screen and graphics controller are linked by LVDS, the LVDS system uses power on every refresh cycle. When idle, the refresh rate of many LCD screens can be dropped to 30 Hz without any noticeable effect (unlike cathode ray tube (CRT) monitors, where a decrease in refresh rate produces a characteristic flicker). The driver for Intel graphics adapters built into the kernel used in Fedora 14 performs this downclocking automatically, and saves around 0.5 W when the screen is idle.
Synchronous dynamic random access memory (SDRAM) — as used for video memory in graphics adapters — is recharged thousands of times per second so that individual memory cells retain the data that is stored in them. Apart from its main function of managing data as it flows in and out of memory, the memory controller is normally responsible for initiating these refresh cycles. However, SDRAM also has a low-power self-refresh mode. In this mode, the memory uses an internal timer to generate its own refresh cycles, which allows the system to shut down the memory controller without endangering data currently held in memory. The kernel used in Fedora 14 can trigger memory self-refresh in Intel graphics adapters when they are idle, which saves around 0.8 W.
Typical graphical processing units (GPUs) contain internal clocks that govern various parts of their internal circuitry. The kernel used in Fedora 14 can reduce the frequency of some of the internal clocks in Intel and ATI GPUs. Reducing the number of cycles that GPU components perform in a given time saves the power that they would have consumed in the cycles that they did not have to perform. The kernel automatically reduces the speed of these clocks when the GPU is idle, and increases it when GPU activity increases. Reducing GPU clock cycles can save up to 5 W.
The Intel and ATI graphics drivers in Fedora 14 can detect when no monitor is attached to an adapter and therefore shut down the GPU completely. This feature is especially significant for servers which do not have monitors attached to them regularly.
Many computer systems contain radio transmitters, including Wi-Fi, Bluetooth, and 3G devices. These devices consume power, which is wasted when the device is not in use.
RFKill is a subsystem in the Linux kernel that provides an interface through which radio transmitters in a computer system can be queried, activated, and deactivated. When transmitters are deactivated, they can be placed in a state where software can reactive them (a soft block) or where software cannot reactive them (a hard block).
The RFKill core provides the application programming interface (API) for the subsystem. Kernel drivers that have been designed to support RFkill use this API to register with the kernel, and include methods for enabling and disabling the device. Additionally, the RFKill core provides notifications that user applications can interpret and ways for user applications to query transmitter states.
The RFKill interface is located at /dev/rfkill, which contains the current state of all radio transmitters on the system. Each device has its current RFKill state registered in sysfs. Additionally, RFKill issues uevents for each change of state in an RFKill-enabled device.
Rfkill is a command-line tool with which you can query and change RFKill-enabled devices on the system. To obtain the tool, install the rfkill package.
blocks the first RFKill-enabled device on the system.
Fedora 14 uses a tickless kernel (refer to Section 3.4, "Tickless Kernel"), which allows the CPUs to remain in deeper idle states longer. However, the timer tick is not the only source of excessive CPU wakeups, and function calls from applications can also prevent the CPU from entering or remaining in idle states. Unnecessary function calls were reduced in over 50 applications.
Input or output (IO) to storage devices and network interfaces forces devices to consume power. In storage and network devices that feature reduced power states when idle (for example, ALPM or ASPM), this traffic can prevent the device from entering or remaining in an idle state, and can prevent hard drives from spinning down when not in use. Excessive and unnecessary demands on storage have been minimized in several applications. In particular, those demands that prevented hard drives from spinning down.
Services that start automatically whether required or not have great potential to waste system resources. Services instead should default to "off" or "on demand" wherever possible. For example, the BlueZ service that enables Bluetooth support previously ran automatically when the system started, whether Bluetooth hardware was present or not. The BlueZ initscript now checks that Bluetooth hardware is present on the system before starting the service.
A typical standard server nowadays comes with basically all of the necessary hardware features supported in Fedora 14. The first thing to take into consideration is the kinds of workloads for which the server will mainly be used. Based on this information you can decide which components can be optimized for power savings.
One other very common place where power management and savings can really make a difference are laptops. As laptops by design normally already use drastically less energy than workstations or servers the potential for absolute savings are less than for other machines. When in battery mode, though, any saving can help to get a few more minutes of battery life out of a laptop. Although this section focuses on laptops in battery mode, but you certainly can still use some or all of those tunings while running on AC power as well.
Savings for single components usually make a bigger relative difference on laptops than they do on workstations. For example, a 1 Gbit/s network interface running at 100 Mbits/s saves around 3–4 watts. For a typical server with a total power consumption of around 400 watts, this saving is approximately 1 %. On a laptop with a total power consumption of around 40 watts, the power saving on just this one component amounts to 10 % of the total.
Configure the system BIOS to disable all hardware that you do not use. For example, parallel or serial ports, card readers, webcams, WiFi, and Bluetooth just to name a few possible candidates.
Dim the display in darker environments where you do not need full illumination to read the screen comfortably. Use System+Preferences → Power Management on the GNOME desktop, Kickoff Application Launcher+Computer+System Settings+Advanced → Power Management on the KDE desktop; or gnome-power-manager or xbacklight at the command line; or the function keys on your laptop.
Use the laptop-battery-powersave profile of tuned-adm to enable a whole set of power-saving mechanisms. Note that performance and latency for the hard drive and network interface are impacted.
Note that USB auto-suspend does not work correctly with all USB devices.
Many applications scan configuration files for changes. In many cases, the scan is performed at a fixed interval, for example, every minute. This can be a problem, because it forces a disk to wake up from spindowns. The best solution is to find a good interval, a good checking mechanism, or to check for changes with inotify and react to events. Inotify can check variety of changes on a file or a directory.
The advantage of this approach is the variety of checks that you can perform.
The main limitation is that only a limited number of watches are available on a system. The number can be obtained from /proc/sys/fs/inotify/max_user_watches and although it can be changed, this is not recommended. Furthermore, in case inotify fails, the code has to fall back to a different check method, which usually means many occurrences of #if #define in the source code.
For more information on inotify, refer to the inotify man page.
Fsync is known as an I/O expensive operation, but this is is not completely true. For example, refer to Theodore Ts'o's article Don't fear the fsync!  and the accompanying discussion.
Firefox used to call the sqlite library each time the user clicked on a link to go to a new page. Sqlite called fsync and because of the file system settings (mainly ext3 with data-ordered mode), there was a long latency when nothing happened. This could take a long time (up to 30 seconds) if another process was copying a large file at the same time.
However, in other cases, where fsync wasn't used at all, problems emerged with the switch to the ext4 file system. Ext3 was set to data-ordered mode, which flushed memory every few seconds and saved it to a disk. But with ext4 and laptop_mode, the interval between saves was longer and data might get lost when the system was unexpectedly switched off. Now ext4 is patched, but we must still consider the design of our applications carefully, and use fsync as appropriate.


text:
Фторирование воды — это контролируемое добавление в водопроводную воду фтора для предотвращения кариеса.

Обработанная вода содержит фтор в количестве, достаточном для предотвращения развития полостей распада в зубах. Когда поступающего в организм естественным путём фтора оказывается мало, его дефицит восполняется из фторированной воды. Фторированная вода оказывает действие через поверхность зуба, сообщая слюне невысокую концентрацию фтора, который снижает вымывание минеральных солей из зубной эмали, и повышает насыщение минералами стенок полостей распада зуба в самом начале их образования.

Обычно в питьевую воду добавляют фторсодержащее вещество. Когда естественное содержание фтора в воде слишком велико, его приходится понижать до допустимого предела. В 1994 году экспертный комитет Всемирной организации здравоохранения установил норму содержания фтора в питьевой воде в пределах 0,5 — 1,0 миллиграмма на литр, в зависимости от климата. В продаваемой в бутылках воде уровень фтора обычно не определяют, а домашние фильтры часто задерживают фтор из водопроводной воды, частично или полностью.

Стоимость обогащения воды фтором в США составляет примерно 0,92 доллара на душу населения в год.

Фторирование воды имеет целью профилактику хронического заболевания, основная тяжесть которого приходится на детей и представителей бедных слоёв населения. Его использование представляет собой пример конфликта между общим благом и правами личности. Фторирование водопроводной воды общего пользования противоречиво, и вызывает возражения, имеющие под собой ряд этических и юридических оснований. Кроме того, существуют мнения о его неэффективности и даже опасности. Однако, учреждения здравоохранения и стоматологии по всему миру подтверждают безопасность и эффективность фторирования питьевой воды, которое началось в 40-е годы XX века, после исследования детей, проживающих в местах, где уровень фтора в воде повышен естественным образом. Исследователи обнаружили, что умеренное потребление фторидов предотвращает кариес, и к 2004 году около 400 миллионов человек были обеспечены фторированной водой.

Цели фторирования воды

Цель фторирования воды — снижение заболеваемости кариесом за счёт регулирования количества фторидов в водопроводной воде. Кариес остаётся одной из главных проблем здравоохранения в большинстве развитых стран мира, в которых им страдают от 60 до 90 % детей школьного возраста и подавляющее большинство взрослого населения. Лечение кариеса обходится обществу дороже лечения любого другого заболевания. Фторирование воды предотвращает кариес как у детей, так и у взрослых. Снижение заболеваемости кариесом за счёт фторирования воды составляет от 18 до 40 % у детей, уже пользующихся зубной пастой и другими источниками фтора. Несмотря на то, что фторирование воды в некоторых случаях может стать причиной флюороза, при котором нарушается прорезывание зубов, большинство случаев флюороза оказываются слабовыраженными, и не рассматриваются как причина эстетических нарушений или повод для обеспокоенности учреждений здравоохранения. Явных признаков других побочных действий фторированной воды нет. Эффективность фторирования доказана исследованиями достаточно высокого качества, тогда как исследования, доказывающие побочные действия, были, в основном, низкого качества. Действие фтора на организм зависит от величины суточной дозы из всех источников, включая фторированные зубную пасту, соль, молоко, и воду, которая обеспечивает бо́льшую часть потребности во фторе. В тех случаях когда фторирование воды технически осуществимо и приемлемо в культурном отношении, оно оказывается очень выгодным, особенно для групп населения с высоким риском кариеса Центры контроля заболеваемости США относят фторирование воды в стране к десятке великих достижений национального здравоохранения 20-го века.. В отличие от США, в большинстве стран Европы существенное снижение заболеваемости кариесом произошло в первую очередь благодаря введению в обиход в 70-е годы XX века фторсодержащих зубных паст. Фторирование воды как главное средство профилактики кариеса в США надо считать оправданным в силу социально-экономического неравенства населения, затрудняющего доступность стоматологической помощи и других способов профилактики кариеса для бедных. Мотивы для фторирования соли или воды сходны с таковыми для йодирования соли, осуществляемого в целях профилактики кретинизма и эндемического зоба.

Способы фторирования воды

Фторирование не изменяет внешний вид, вкус и запах воды . Обычно фторирование осуществляют добавлением в воду одного из трёх веществ: фторида натрия, фторкремниевой кислоты или фторсиликата натрия.
 Фторид натрия (NaF) был первым веществом, применённым для фторирования воды, и теперь считается эталоном, по которому рассчитывают нормы фторирования. Это белое порошкообразное или кристаллическое вещество без запаха. Кристаллическая форма предпочтительнее, когда работа выполняется вручную, потому что кристаллы меньше пылят. Фторид натрия дороже других веществ для фторирования, но он удобен в работе, и поэтому чаще всего используется на мелких предприятиях коммунального обслуживания.
 Фторкремниевая кислота (H2SiF6) — недорогая жидкость, которая образуется в процессе производства фосфорных удобрений. Её поставляют в разных концентрациях, от 23 до 25 %. Из-за большого содержания воды её транспортировка обходится дорого. Другие названия этого вещества — фторокремниевая кислота, гексафторкремниевая кислота, кремнефтористоводородная кислота, кремнефтористая кислота.
 Фторсиликат натрия (Na2SiF6) — это порошок или очень мелкие кристаллы, транспортировать его значительно легче, чем фторкремниевую кислоту.

Эти вещества используют для фторирования из-за их хорошей растворимости, безопасности, доступности и дешевизны. По данным исследования в 1992 году отчётов компаний — владельцев водопроводных систем в США оказалось, что 63 % населения получали воду, фторированную фторкремниевой кислотой, 28 % — фторсиликатом натрия, а 9 % — фторидом натрия. Центры контроля и профилактики заболеваний США разработали рекомендации для фторирования воды, определяющие требования к персоналу, отчётность, обучение, надзор, инспектирование, наблюдение, меры в случае превышения концентрации наряду с техническими требованиями для каждого из основных применяемых для фторирования веществ.

В США норма содержания фтора в водопроводной воде колеблется в пределах от 0,7 до 1,2 миллиграмма на литр, (что соответствует 0.7 — 1.2 частей на миллион), в зависимости от средней максимальной температуры воздуха. В местах с более тёплым климатом, где люди пьют больше воды, уровень фтора поддерживают ниже, а в прохладном — выше. Принятый в 1962 году стандарт США не применим для всего мира, поскольку он основывается на расчётах, устаревших из-за всё большего распространения систем кондиционирования воздуха, увеличения потребления безалкогольных напитков, переработанных пищевых продуктов -полуфабрикатов и готовых к употреблению продуктов, а также других источников фтора. В 1994 году экспертная комиссия Всемирной организации здравоохранения по применению фтора постановила считать концентрацию фтора в воде 1,0 миллиграмм на литр верхней границей даже для мест с холодным климатом, а нижней границей была объявлена концентрация 0,5 миллиграмма на литр В 2007 году Австралийский систематический обзор рекомендовал диапазон концентраций фтора от 0.6 до 1.1 мг/л..

Вода в естественных источниках содержит разные количества фтора, где-то уровень находится в пределах нормы, где-то мал, или, наоборот, очень высок. В реках и озёрах фтора, как правило, мало, меньше чем 0,5 миллиграмма на литр, а вода подземных источников, особенно в вулканических и горных районах может содержать до 50 миллиграмм фтора в литре. Повышенные концентрации фтора характерны для щелочных вулканических пород, гидротермальных вод, гидротермальных рудных месторождений, осадочных и других пород, произошедших из старой, изменённой гидротермальной циркуляцией магмы в процессе рудообразования под влиянием гидротермальных процессов, образующих гидротермальные растворы, из которых фтор попадает в прилегающие водоёмы в виде фторидов. В большей части питьевой воды до 95 % фтора содержится в виде иона F−, следом за ним идёт комплексный ион фторид магния-complex (MgF+). Поскольку уровень фтора в воде определяется растворением флюорита (CaF2), повышенное содержание фторидов обычно бывает в бедных кальцием, мягких, со щелочной средой водах, которые лучше растворяют флюорит. Освобождать воду от фтора приходится, когда его содержание превышает рекомендуемые пределы. Фтор из воды можно убрать, пропуская её через слой активированного глинозёма, костной муки, костного угля или трикальцийфосфата, или коагуляцией алюмокалиевыми квасцами или осаждением известью.

Бытовые водяные фильтры разных конструкций — фильтры-кувшины, фильтры, монтируемые непосредственно на кран — не изменяют концентрацию фтора. Более дорогие фильтры, работающие по принципу обратного осмоса, удаляют 65-95 % фтора, а дистилляция освобождает воду от фтора полностью. В США действующие нормативы не предусматривают обязательного указания производителем содержания соединений фторидов в бутилированной воде, поэтому влияние такой воды на здоровье не всегда можно предсказать. Исследование бутилированной воды в штатах Айова и Кливленд показали недостаточное содержание в ней фторидов. исследование, проведённое в Сан-Паулу, показало наличие значительного расхождения в содержании фторидов между нормативами, фактическим содержанием и указанными на этикетке данными.

Культурное влияние
 Генерал Джек Д. Риппер, герой фильма Доктор Стрейнджлав, или как я перестал бояться и полюбил бомбу, считал фторирование воды вероломными происками русских коммунистов, что явилось одной из причин, подвигших его к использованию служебного положения и отдаче приказа к нападению на СССР.

Примечания

Вода
Жилищно-коммунальное хозяйство
Зубы
Стоматология
Фтор
Фторирование

redpajama_set_name: RedPajamaWikipedia


text:
India: Rohingya have 'terror' ties
In court case on expelling 40,000 Rohingya, home ministry cites secret evidence showing links to armed groups.
Demonstrators in New Delhi shout slogans against the killing of Rohingya in Myanmar last week [Adnan Abidi/Reuters]
India's government said on Monday it has evidence showing some Rohingya in the country have ties to "terror organisations" and pose a security threat that justifies a mass deportation of the ethnic group.
India's home ministry said it would confidentially share intelligence information with the Supreme Court showing Rohingya links with Pakistan-based armed groups, in a bid to get legal clearance for plans to deport 40,000 Rohingya.
The Supreme Court is hearing an appeal lodged on behalf of Rohingya against the deportation plan proposed by Prime Minister Narendra Modi's Hindu nationalist government.
India's home ministry submitted an affidavit to the court arguing the hardline stance was justified by the security threat posed by illegal immigrants from the majority-Muslim Rohingya ethnic group, hundreds of thousands of whom have fled from Myanmar to Bangladesh, from where many have crossed into India.
"The court has no business to interfere in such matters of what they call illegal immigrants or illegal migrants," the government said in the affidavit.
READ MORE: Cox's Bazar - Chaos all around at Rohingya camps
Additional Solicitor-General Tushar Mehta told the court the government would provide evidence of Rohingya links with "extremist groups" and illegal transfers of money at the next hearing.
The lawyer representing the Rohingya denounced the move.
WATCH: India court to hear petition challenging Rohingya refugees' deportation
"This is clearly a case of religious discrimination and an attempt to arouse an anti-Muslim feeling," Prashant Bhushan said.
The ministry said the influx of large numbers of Rohingya into India began four to five years ago, long before an exodus that saw more than 400,000 Rohingya flee to Bangladesh since August 25 to escape a Myanmar military offensive that the United Nations has called "ethnic cleansing".
The affidavit went on to say the government had reports from security agencies and other credible sources "indicating linkages of some of the unauthorised Rohingya immigrants with Pakistan-based terror organisations and similar organisations operating in other countries".
It also said there was information on Rohingya involvement in plots by the Islamic State of Iraq and the Levant (ISIL, also known as ISIS) and other "extremist groups" to ignite communal and sectarian violence in India.
Senior home ministry official Mukesh Mittal said the Indian government would privately show the court material gathered from "sensitive investigations" to substantiate the claims in its affidavit.
Bhushan will file a rejoinder to the government's affidavit, his office told Reuters news agency.
The court will next hear the matter on October 3.
Meanwhile, police said on Monday they had arrested a suspected member of al-Qaeda who they believed was trying to recruit Rohingya living in India to fight security forces in Myanmar.
Senior police officer Pramod Kushwaha said British national Shauman Haq, 27, was arrested near a bus stop in New Delhi on Sunday. He had come to India via Bangladesh.
Myanmar: Who are the Rohingya?
Rohingya in India voiced worries that they were being unfairly tainted by the allegations and sought more understanding for their plight.
"We feel helpless and hopeless," said Rohingya youth leader Ali Johar, who came to India in 2012 and lives with his family in a Delhi settlement.
"The world's largest democracy has given us shelter, but they should handle this situation more empathetically."
Modi's government has been criticised by activists for not speaking out against Myanmar's recent military offensive against Rohingya fighters, and right-wing groups in India have begun vilifying Rohingya living there.
The Rohingya are denied citizenship in Buddhist-majority Myanmar and regarded as illegal immigrants, despite claiming roots that date back centuries. More than 800,000 Rohingya currently live in Bangladesh.
THE LISTENING POST: Covering the Rohingya - Separating fact from fiction
SOURCE: News agencies


Supports Flickr & Google Photos.
Automatically generates a thumbnail grid layout on the webpage.
Clicks on the thumbnail to view all the images in a lightbox popup.
Tons of configuration options, API methods and events.
data-ngid: Item ID. MANDATORY if albums used: please set a value to each item (image and album).
data-ngalbumid: ID of the album containing the item. MANDATORY if albums used.
data-ngkind: Item's kind. Possible values: 'image', 'album'.
data-ngthumb: URL of the thumbnail image.
data-ngthumbImgHeight: Height of the thumbnail image (in pixels). Not mandatory, but should be defined to improve overall performances.
data-ngthumbImgWidth: Width of the thumbnail image (in pixels). Not mandatory, but should be defined to improve overall performances.
data-ngdest: Destination URL on thumbnail click (instead of displaying an image, the user is redirected to the defined URL).
data-ngexiflocation: Exif location - this value is used to display the image location with Google Maps on the image info window.
shoppingCartGet: Returns an array containing all the items in the shopping cart. One item content: idx=internal index, ID=your image ID, cnt=counter.
displayItem: Displays an item (album or image).
reload: Reloads the current album.
option: Returns the value of an option.
new_value: Sets the value of an option (note: only some options are supported).
getItem: Returns one item (object) - can be one image or one album.
getItems: Returns an array with all the items (array of objects).
getItemsIndex: Returns an array containing the indexes of the items.
itemsSelectedGet: Returns an array with all the selected items (array of objects).
itemsSetSelectedValue: Sets/unsets selection value (true/false) of an array of items.
closeViewer: Close the image viewer.
minimizeToolbar: Minimize image viewer toolbar.
maximizeToolbar: Maximize image viewer toolbar.
pageChanged.nanogallery2: Fired on gallery pagination.
galleryRenderStart.nanogallery2: The rendering of the gallery is started.
galleryRenderEnd.nanogallery2: he galelry has been rendered.
galleryObjectModelBuilt.nanogallery2 : The Gallery Object Model(GOM) has been populated with all the items.
galleryLayoutApplied.nanogallery2: The layout has been applied to the gallery/thumbnails.
galleryDisplayed.nanogallery2: The thumbnails have been displayed.
lightboxNextImage.nanogallery2: Lightbox - display next image.
lightboxPreviousImage.nanogallery2: Lightbox - display previous image.
lightboxImageDisplayed.nanogallery2: Lightbox - image displayed.
shoppingCartUpdated: Called when the shopping cart is updated (new item or item updated).
This awesome jQuery plugin is developed by nanostudio. For more Advanced Usages, please check the demo page or visit the official website.


text:
Q: DropSolve Cplex terminate after T time I am using drop solve for a MIP optimization problem, to generate K solutions.
I would like to terminate after 60 seconds. I use cplex.params[1039] = 60; Also tried cplex.tilim = 60 in my .mod file
But the program doesn't stops.
Found this SO link to do the same in Java, but I am using DropSolve DoCplex Cloud. Using the Java API's
Terminate and retrieve solution in ILOG after a certain time limit
TIA

A: I answered the question on the docplexcloud forum https://developer.ibm.com/answers/questions/385233/dropsolve-cplex-terminate-after-t-time.html.
The engine respects the parameter settings but the .mod file executes some scripting code after the solve. Execution of that code takes longer than expected but this is beyond the control of the engine and its parameters.

redpajama_set_name: RedPajamaStackExchange


After writing about critical thinking recently, I received an outstanding question: how exactly might an adult who never had the opportunity for any sort of formal training in critical thinking during school learn about it now? It is never too late to learn, and few things are more important to learn than critical thinking.
You can also find quite a bit of worthwhile information at The Critical Thinking Community. For example, here's a module called Critical Thinking in Everyday Life: 9 Strategies.
I hope this helps. If you find alternatives you like, let us know in the comments.