Friday, 7 April 2017

Google Details Tensor Chip Powers


In January’s special Top Tech 2017 issue, I wrote about various efforts to produce custom hardware tailored for performing deep-learning calculations. Prime among those is Google’s Tensor Processing Unit, or TPU, which Google has deployed in its data centers since early in 2015.

In that article, I speculated that the TPU was likely designed for performing what are called  “inference” calculations. That is, it’s designed to quickly and efficiently calculate whatever it is that the neural-network it’s running was created to do. But that neural network would also have to be “trained,” meaning that its many parameters would be tuned to carry out the desired task. Training a neural network normally takes a different set of computational skills: In particular, training often requires the use of higher-precision arithmetic than does inference.

Yesterday, Google released a fairly detailed description of the TPU and its performance relative to CPUs and GPUs. I was happy to see that the surmise I had made in January was correct: The TPU is built for doing inference, having hardware that operates on 8-bit integers rather than higher-precision floating-point numbers.

Yesterday afternoon, David Patterson, an emeritus professor of computer science at the University of California, Berkeley and one of the co-authors of the report, presented these findings at a regional seminar of the National Academy of Engineering, held at the Computer History Museum in Menlo Park, Calif. The abstract for his talk summed up the main point nicely. It reads in part: “The TPU is an order of magnitude faster than contemporary CPUs and GPUs and its relative performance per watt is even larger.”

Google’s blog post about the release of the report shows how much of a difference in relative performance there can be, particularly in regard to energy efficiency. For example, compared with a contemporary GPU, the TPU is said to offer 83 times the performance per watt.  That might be something of an exaggeration, because the report itself claims only that there’s a range of between 41 times and 83 times. And that’s for a quantity the authors call incremental performance. The range of improvement for total performance is less: from 14 to 16 times better for the TPU compared with that of a GPU.

The benchmark tests used to reach these conclusions are based on a half dozen of the actual kinds of neural-network programs that people are running at Google data centers. So it’s unlikely that anyone would critique these results on the basis of the tests not reflecting real-world circumstances. But it struck me that a different critique might well be in order.

The problem is this: These researchers are comparing their 8-bit TPU with higher-precision GPUs and CPUs, which are just not well suited to inference calculations. The GPU exemplar Google used in its report is Nvidia’s K80 board, which performs both single-precision (32-bit) and double-precision (64-bit) calculations. While they’re often important for training neural networks, such levels of precision aren’t typically needed for inference.

In my January story, I noted that Nvidia’s newer Pascal family of GPUs can perform “half-precision” (16-bit) operations and speculated that the company may soon produce units fully capable of 8-bit operations, in which case they might be much more efficient when carrying out inference calculations for neural-network programs.

The report’s authors anticipated such a criticism in the final section of their paper; there they considered the assertion (which they label a fallacy) that “CPU and GPU results would be comparable to the TPU if we used them more efficiently or compared to newer versions.” In discussing this point, they say they had tested only one CPU that could support 8-bit calculations, and the TPU was 3.5 times better. But they don’t really address the question of how GPU’s tailored for 8-bit calculations would fare—an important question if such GPUs soon became widely available.

Should that come to pass, I hope that these Googlers will re-run their benchmarks and let us know how TPUs and 8-bit-capable GPUs compare.



Read the full article here by Computing: IEEE Spectrum

The iPhone 7 Has Arbitrary Software Locks That Prevent Repair

Jason Koebler, reporting for Motherboard: Apple has taken new and extreme measures to make the iPhone unrepairable. The company is now using software locks to prevent independent repair of specific parts of the phone. Specifically, the home buttons of the iPhone 7 and iPhone 7 Plus are not user replaceable, raising questions about both the future repairability of Apple products and the future of the thriving independent repair industry. The iPhone 7 home button will only work with the original home button that it was shipped with; if it breaks and needs to be replaced, a new one will only work if it is "recalibrated" in an Apple Store.
Share on Google+

Read more of this story at Slashdot.



Read the full article here by Slashdot

NVIDIA's "Open-Source Guy" Has Left The Company

One of the main public-facing figures to NVIDIA's open-source driver efforts has left the company to pursue a new opportunity.

Alexandre Courbot is likely a name you've crossed before if reading our past articles when it comes to NVIDIA code contributions to Nouveau, NVIDIA releasing signed firmware files, and occasional commentary on the mailing lists. Last Friday was his final day with NVIDIA.

Courbot wrote on

Google+

, "It was a difficult decision to make, but after an awesome 6 years ride with NVIDIA I have decided to move to new adventures...I consider myself particularly lucky that on top of working for one of the top employers in our field, I also got the chance for the last 3 years to work directly with one of the most welcoming and technically gifted OSS communities."

He also took this opportunity to praise the work done by the Nouveau community in working on an open-source NVIDIA driver. "

One cannot really appreciate what the Nouveau project has achieved without looking closely at the driver itself and understanding how a handful of people maintain a graphics driver that supports virtually all generations of NVIDIA GPUs. This is an incredible feat that is sadly sometimes met with skepticism or ungratefulness, while it should simply inspire our respect.

"

Alexandre Courbot was the one who led the charge on

releasing the Maxwell and Pascal firmware

,

changes to Nouveau

, a lot of Tegra work, and

much more

. Hopefully NVIDIA has someone very capable to replace him and continue interacting with Nouveau. He's far from the only NVIDIA open-source/Linux developer at the company, but was one of the few public-facing developers interacting directly with Nouveau the past few years.

He also added, "

On top of the technical quality of the project, it has been so much fun to work and chat with the Nouveau team. Hopefully this fun will continue as my next work should remain within the same extended community, although I am unlikely to directly work with Nouveau anymore.

" As far as where he's going next, he hasn't revealed. But before any speculations about him going to AMD or Valve based upon his comments about staying within the same extended community, in the comments he mentions he is staying within Japan.



Read the full article here by Phoronix

L’etichetta Fact Check da oggi disponibile in tutti i paesi nella ricerca Google e in Google News

Google è stata creata con l’obiettivo di aiutare gli utenti a trovare informazioni utili, offrendo visibilità ai contenuti che gli editori creano.

Tuttavia, con migliaia di nuovi articoli pubblicati online ogni minuto di ogni giorno, la quantità di contenuti con cui si confrontano gli utenti può risultare eccessiva. E purtroppo, non tutti questi contenuti sono aderenti ai fatti o veri, rendendo così difficile per i lettori distinguere i fatti da ciò che è falso. Ecco perché ad ottobre, insieme ai nostri partner di Jigsaw, abbiamo annunciato che in alcuni Paesi avremmo iniziato a consentire agli editori di mostrare l’etichetta "Fact Check" in Google News. Questa etichetta consente di identificare in modo più immediato gli articoli di verifica dei fatti.

Dopo aver valutato i riscontri ricevuti da parte degli utenti e degli editori, abbiamo deciso di rendere disponibile l’etichetta Fact Check in Google News ovunque e di estenderla al motore di ricerca, a livello globale e in tutte le lingue. Per la prima volta, quando viene effettuata una ricerca su Google che restituisce un risultato che contiene la verifica dei fatti di uno o più affermazioni pubbliche, questa informazione verrà chiaramente visualizzata nella pagina dei risultati di ricerca. Lo snippet mostrerà informazioni sulla dichiarazione verificata, da chi è stata fatta e se una fonte ha verificato quella particolare dichiarazione.



Queste informazioni non saranno disponibili per qualsiasi risultato e potrebbero esserci pagine di risultati di ricerca in cui diverse fonti hanno verificato la stessa affermazione raggiungendo però conclusioni diverse. Queste verifiche dei fatti naturalmente non sono effettuate da Google e potremmo anche non essere d'accordo con i risultati, proprio come diversi articoli di fact checking potrebbero essere in disaccordo tra loro, tuttavia riteniamo che sia utile per le persone capire il grado di consenso attorno a un argomento e avere informazioni chiare su quali fonti concordano. Rendendo queste attività di fact checking più visibili nei risultati di ricerca, riteniamo che gli utenti possano esaminarle e valutarle con maggiore facilità per formarsi così opinioni e pareri informati.

Per poter usufruire di questa etichetta, gli editori devono utilizzare il markup ClaimReview di Schema.org sulle pagine nelle quali effettuano il fact checking di dichiarazioni pubbliche (informazioni maggiori qui) o usare il widget Share the Facts sviluppato dal Duke University Reporters Lab e Jigsaw. Solo gli editori che sono algoritmicamente determinati come fonte autorevole di informazioni si qualificheranno per essere inclusi. Infine, i contenuti dovranno rispettare le norme generali che si applicano a tutti i tag di dati strutturati e ai criteri di Google News Publisher per il fact checking. Se un editore o un articolo di fact checking non raggiunge questi standard o non rispetta tali norme, potremo, a nostra discrezione, ignorare il markup.



Tutto ciò non sarebbe stato possibile senza l'aiuto di altre organizzazioni e senza il sostegno della comunità di fact checking, che è cresciuta fino a includere più di 115 organizzazioni. Se volete saperne di più visitate il nostro Centro assistenza per gli utenti.

Scritto da: Justin Kosslyn (Product Manager, Jigsaw) e Cong Yu (Research Scientist, Google Research) Justin Kosslyn, Cong YuProduct Manager, Research ScientistJigsaw, Google Research


Read the full article here by Google Italia Blog

Wednesday, 5 April 2017

Ubuntu Unity is dead: Desktop will switch back to GNOME next year

Security Advice

Never give your password or bank account number to anyone who doesn't have a blue check mark next to their name.

Read the full article here by xkcd.com

Everything is broken

Once upon a time, a friend of mine accidentally took over thousands of computers. He had found a vulnerability in a piece of software and started playing with it. In the process, he figured out how to get total administration access over a network. He put it in a script, and ran it to see what would happen, then went to bed for about four hours. Next morning on the way to work he checked on it, and discovered he was now lord and master of about 50,000 computers. After nearly vomiting in fear he killed the whole thing and deleted all the files associated with it. In the end he said he threw the hard drive into a bonfire. I can't tell you who he is because he doesn't want to go to Federal prison, which is what could have happened if he'd told anyone that could do anything about the bug he'd found. Did that bug get fixed? Probably eventually, but not by my friend. This story isn't extraordinary at all. Spend much time in the hacker and security scene, you'll hear stories like this and worse. It's hard to explain to regular people how much technology barely works, how much the infrastructure of our lives is held together by the IT equivalent of baling wire. Computers, and computing, are broken. It's from 2014, but drop everything you're doing right now and read this. Go on. Don't put it off. Read it.

Read the full article here by OSNews

Security Researcher Says Samsung's Tizen OS Is The Worst Code He's Ever Seen

Samsung has been working on its Tizen operating system for several years now, implementing it into its various televisions and smartwatches. According to a report from Motherboard, the OS isn't receiving a lot of praise in the security department. Israeli researcher Amihai Neiderman has found 40 unknown zero-day vulnerabilities in Tizen, adding that it may be the worst code he's ever seen. From the report: "It may be the worst code I've ever seen," he told Motherboard in advance of a talk about his research that he is scheduled to deliver at Kaspersky Lab's Security Analyst Summit on the island of St. Maarten on Monday. "Everything you can do wrong there, they do it. You can see that nobody with any understanding of security looked at this code or wrote it. It's like taking an undergraduate and letting him program your software." All of the vulnerabilities would allow hackers to take control of a Samsung device from afar, in what's called remote-code execution. But one security hole Neiderman uncovered was particularly critical. It involves Samsung's TizenStore app -- Samsung's version of Google Play Store -- which delivers apps and software updates to Tizen devices. Neiderman says a flaw in its design allowed him to hijack the software to deliver malicious code to his Samsung TV. Because the TizenStore software operates with the highest privileges you can get on a device, it's the Holy Grail for a hacker who can abuse it. Although TizenStore does use authentication to make sure only authorized Samsung software gets installed on a device, Neiderman found a heap-overflow vulnerability that gave him control before that authentication function kicked in. Although researchers have uncovered problems with other Samsung devices in the past, Tizen has escaped extensive scrutiny from the security community, probably because it's not widely used on phones yet.
Share on Google+

Read more of this story at Slashdot.



Read the full article here by Slashdot

Monday, 3 April 2017

Nuclear power policy in the ’80s caused low birth weights after coal stepped in

Smartphone 5.1" Huawei P10 64Go (avec 100€ minimum pour la reprise d'un ancien téléphone) à 499€ en magasin @ Boulanger

499€
599.00€ (-17%)
Localisation : National Boulanger nous ressort le même type d'opération que celle avec le S7 mais cette fois ci pour le Huawei P10.

Vous ramenez un téléphone et vous avez donc une reprise minimum de 100€ + le prix de reprise de votre téléphone soit déjà 499€ maximum (exemple: reprise de 50€ de votre téléphone soit 100€+50€=150€ donc plus que 449€ à payer en caisse)
Soit le P10 à MAXIMUM 499€(449€ dans l'exemple)

PAS BESOIN DE PRENDRE LA CARTE BOULANGER ET REMISE DE REPRISE IMMÉDIATE !!!!

Preuve de la reprise : https://www.bou[...]17TABP.pdf


CARACTÉRISTIQUES TECHNIQUES

Système Android 7.0
Interface utilisateur Huawei Emotion UI
Processeur HiSilicon Kirin 960
Nombre de coeurs 8
Fréquence processeur 2.4 GHz
Puce graphique ARM Mali G71 MP8
Support cartes mémoire Oui
Type de cartes supportées microSD, microSDHC, microSDXC
Mémoire vive (RAM) 4 Go
Capacité 64 Go
Mémoire flash Libre 52.6 Go
Indice DAS 0.96 W/kg
Indice de protection (étanchéité) Aucun
Double SIM Non
AFFICHAGE

Taille (diagonale) 5.1 "
Technologie de l'écran IPS
Définition de l'écran 1920 x 1080 px
Résolution de l'écran 432 ppp
ENTRÉES & SORTIES

Support du Wi-Fi Oui
Norme Wi-Fi Wi-Fi 802.11ac
Support du Bluetooth Oui
Version Bluetooth Bluetooth 4.2
Support du NFC Oui
Support de l'infra-rouge (IrDA) Non
Type de connecteur USB USB Type-C
Compatibilité USB Host Oui
MULTIMÉDIA

Capteur photo principal 20 Mpx
Flash Oui
Enregistrement vidéo (principal) 3840 x 2160 px
Capteur en façade Oui
Définition vidéo du capteur en façade 1920 x 1080 px
Capteur photo frontal 8 Mpx
Radio FM Non
COMMUNICATION

Bandes GSM 850 MHz, 900 MHz, 1800 MHz, 1900 MHz Mhz
Compatible réseau 4G (LTE) Oui
ALIMENTATION

Batterie amovible Non
Capacité de la batterie 3200 mAh
DIMENSIONS

Largeur 6.93 cm
Hauteur 14.53 cm
Epaisseur 0.698 cm
Volume 70.2836442 cm3
Poids 145 g


Read the full article here by Dealabs.com

T-Rex Wine Bottle Holders

Atlantic Collectibles has released an awesome T-Rex Dinosaur Wine Bottle Holder. It look like a deadly Tyrannosaurus rex is lying on its back, chugging your wine. They come in two varieties: alive ($24), and dead ($32). It is available to purchase from Amazon...(Read...)



Read the full article here by Likecool

Tame Microsoft's snooping with Windows Privacy Tweaker

Windows Privacy Tweaker is an easy-to-use portable application for viewing and controlling more than 50 Windows telemetry and privacy settings. Unlike many similar programs, this isn’t just for Windows 10. You’ll be able to see and toggle some settings on anything from Windows Vista up. The program starts with an offer to create a System Restore Point when it loads. Accept this and you should easily be able to undo your changes later Windows Privacy Tweaker organizes its settings into three categories. "Services" lists Windows services, including Remote Registry and Remote Desktop; "Scheduler" lists Windows scheduled tasks relating to Microsoft’s… [Continue Reading]


Read the full article here by Betanews

Galaxy S8 face recognition already defeated with a simple picture

Android handsets could have soft-button fingerprint sensors by year-end

Sunday, 2 April 2017

Android Wear 2.0 is hitting more watches today

Yesterday, Google said that an unspecified bug was delaying the Android Wear 2.0 rollout yet again. It looks like the delay hasn't been too severe, though. The company says that Wear 2.0 is now available for five more watches: the Polar M600, Nixon Mission, Fossil Q Wander, Fossil Q Marshal and Michael Kors Access. That's in addition to the Fossil Q Founder, Casio Smart Outdoor Watch WSD-F10 and TAG Heuer Connected, which Google said were already receiving the update. All told, that's almost half of the 19 older watches that'll get the Wear 2.0 update.

It's a shame the Android Wear 2.0 rollout has been so challenging -- many, many other devices won't ever receive the update. Those that are getting it have had to wait a long time, too, but it seems like it won't be too long until the whole group gets the new software. It makes the platform a lot better, though smartwatches remain a niche. If you really want Wear 2.0, though, your best bet is probably checking out one of LG's newest smartwatches.



Read the full article here by Engadget

Microsoft Is Shutting Down CodePlex

Microsoft corporate vice president Brian Harry announced in a blog post today that they are shutting down CodePlex, its service for hosting repositories of open source software. "As of this post, we've disabled the ability to create new CodePlex projects," Harry wrote. "In October, we'll set CodePlex to read-only, before shutting it down completely on December 15th, 2017." VentureBeat reports: While people will be able to download an archive of their data, Microsoft is teaming up with GitHub, which provides similar functionality for hosting code that people can collaborate on, to give users "a streamlined import experience" to migrate code and related content there. "Over the years, we've seen a lot of amazing options come and go but at this point, GitHub is the de facto place for open source sharing and most open source projects have migrated there," Harry wrote. Microsoft has been leaning in more and more to GitHub in the past few years. It moved the CNTK deep learning toolkit from CodePlex to GitHub last year. Today Microsoft's GitHub organization has more than 16,000 open source contributors, Harry wrote. And last year GitHub itself made a big deal about Microsoft's adoption of GitHub. At the same time, CodePlex has rotted. In the past month people have made commits to fewer than 350 projects, Harry wrote. GitHub is based on the Git open source version control software, which keeps track of changes by multiple people. People can move code to alternative systems like Atlassian's Bitbucket and Microsoft's Visual Studio Team Services, Harry wrote. The startup GitLab also offers hosting for open and closed source projects. Slashvertisement: Here is SourceForge's message to CodePlex devs.
Share on Google+

Read more of this story at Slashdot.



Read the full article here by Slashdot

Exploit attacks your smart TV through over-the-air signals

Worries that someone could hijack your TV with a broadcast have been present for decades (ever see The Outer Limits?), and it's clear that they're not going away any time soon. Oneconsult security researcher Rafael Scheel has outlined an attack that can control smart TVs by embedding code into digital (specifically, DVB-T) over-the-air broadcasts. The intrusion takes advantage of flaws in a set's web browser to get root-level access and issue virtually any command. You only need to have a transmission powerful enough to reach compatible TVs, and at least one attack will work without revealing that something is wrong.

The technique is known to work on at least two recent Samsung models, and it's possible to alter the code to compromise other web-enabled TVs.

If there's a saving grace, it's the specificity of the attack. Only some countries use DVB-T, and fewer still support the hybrid broadcast broadband TV format (HbbTV) needed to make this work. The victim also needs to both be tuned into a DVB-T channel and have the TV connected to the internet. North Americans watching ATSC broadcasts have nothing to worry about right now, in other words, and you're also safe if you use a game console or media hub for your living room entertainment.

The discovery nonetheless underscores the importance of locking down smart TVs, which don't usually receive security updates as frequently as phones or PCs. It's one thing when hackers compromise individual TVs through conventional internet-only attacks, but it's that much more sinister when they can compromise multiple TVs within a certain range. Manufacturers will need to treat security as a higher priority if they're going to prevent attacks like this from happening in the real world.

Via: Ars Technica

Source: Oneconsult AG (YouTube)



Read the full article here by Engadget

Roland founder and music legend Ikutaro Kakehashi dies

It's a tragic time for both music and technology. Ikutaro Kakehashi, best known as the founder of Roland Corporation, has died at 87. The engineer turned corporate leader got his start making electronic drums and rhythm pattern generators, but it was after he founded Roland in 1972 that he hit the big time. His company quickly became synonymous with electronic music effects, and the machines built under his watch didn't just become popular -- they changed the cultural landscape.

Electronic music, '80s pop and hip-hop in particular owe a lot to Kakehashi's firm. The TR-808's unique 'sizzling' drum and hand clap sounds were crucial to genre-defining songs from the likes of Afrika Bambaataa and Nine Inch Nails, and it's so iconic that artists have sometimes based their albums or even careers around it. Think 808 State, or Kanye West's 808s and Heartbreak. And that was really just the start of Kakehashi's biggest accomplishments.

He also got the ball rolling on MIDI, the standard that helped kickstart digital music composition. The TR-909 (the first drum machine to use MIDI) and TB-303 bass synth were crucial to modern dance music's early days, launching genres like acid house. And many PC gamers will have a soft spot for the SC-55 Sound Canvas, the first General MIDI sound card. It was a big step toward computer-based tunes that sounded as good as what you heard from recording studios, and represented PC music's gold standard for years.

Kakehashi gradually bowed out of his company, retiring in 2013, but not before receiving honors ranging from a Technical Grammy through to a spot on Hollywood's Rock Walk of Fame. In some ways, those accolades almost sell him short. While Kakehashi wasn't as singularly responsible for redefining music as someone like synthesizer pioneer Bob Moog, it's safe to say that the industry would have gone in a very, very different direction if he hadn't been around. He'll be missed.

Source: BBC



Read the full article here by Engadget

Windows open UDP and TCP connections analysis using Elastic stack

I've been wondering how many UDP and TCP connection were active when using my PC during daily usage...

How to collect stats

In Windows, you have several ways to collect UDP and TCP connections:

  • netstat -anb (and variants), available using command line
  • tcpvcon -acn (and variants), free and available from Microsoft
  • currports, free and available at Nirsoft website
You can do pretty the same on Linux using netstat or lsof...
I choose currports since it has a rich set of data available in output, such as process names, service name, etc...

You can just run it and perform the following steps:
  • File - Advanced Options and set the pattern specified in currports-log-format
  • Options - Auto Refresh - 4s
  • File - Log Changes
The file should be populated with some network information as in this sample.

How to parse the CurrPorts log

Logstash to the rescue!
I'm not covering the part on how to install it, since everything will work out of the box. The official documentation is quite rich.

You have to provide 2 files:
I am resolving hostnames and enriching the data with GeoIP information, thanks to the Logstash filters.

You have to adjust the file path in the logstash pipeline configuration file to match the location you placed the 2 files in your system.

To see what will be sent to Elasticsearch, uncomment the line stdout { codec => rubydebug } in the output section.
Once you're done you can try to run:
logstash -f logstash-netstat.conf
You should see something like this:
...{
            "Added_On" => 2017-04-02T17:20:04.000Z,
          "Local_Port" => "55572",
    "Remote_Host_Name" => "...",
          "Event_Type" => "Removed",
       "Local_Address" => "127.0.0.1",
          "Process_ID" => "0",
                "path" => "...\\cports-x64\\cports.log",
        "Process_Name" => "Unknown",
          "@timestamp" => 2017-04-02T17:22:04.000Z,
      "Remote_Address" => "127.0.0.1",
               "State" => "Time Wait",
         "Remote_Port" => "55573",
            "@version" => "1",
                "host" => "LUCA-PC",
            "Protocol" => "TCP"
}
{
              "Added_On" => 2017-04-02T17:22:00.000Z,
               "Company" => "Oracle Corporation",
            "Local_Port" => "55757",...

How to visualize the data

You have to install Elasticsearch and Kibana, even on another machine (or use a remote instance on Elastic Cloud...).

In case you want to show a Tile Map, you'll have to tweak few lines in the Kibana configuration file (see here to use OpenStreetMaps).

Create view visualizations:
  • a tag cloud on the Process_Name field
  • a Tile Map on the Remote_Address_Geo.location field
  • an histogram with counts
And you'll get a dashboard!


All necessary files are available on GistHub.