en4bz

All this on Samsung 8nm (~61 MT/mm2). They didn't even feel the need to use TSMC 7nm (~100 MT/mm2). Probably keep the price down and to reserve capacity at TSMC for the A100.

This is like the anime hero/villain (depending on your perspective) equivalent of fighting at half power.

NO_HZ_FULL only works on Fedora and RHEL/CentOS 7+ unfortunately. Not sure why Debian derivatives haven't enabled this feature in the kernel.

1.1.1.1 is dropping ICMP pings while 8.8.8.8 is not but 8.8.8.8 is still returning DNS errors.

There's a reason this as filed in the southern district of NY [1]. IA will lose based on the results of the Redigi case. The court found that in the case of a digital phonorecord that the "tangible medium" was the hard drive of the device it was downloaded to. Thus if you want to resell an MP3 you need to sell your hard drive. You can't just copy it to someone else's and then delete it. Any copy other than the original was found to be an illegal copy.

They never even looked at First Sale Doctrine which is a possible defense in this type of dispute.

If you translate this too books then the book itself is the tangible medium. Scans are infringing copies and only valid for personal use.

[1] https://en.wikipedia.org/wiki/Capitol_Records,_LLC_v._ReDigi...

If you do not register your work with the US Copyright Office you can not claim statutory damages in a lawsuit, only real damages.

> During the gold rush it's a good time to be in the pick and shovel business

Can someone create an equivalent of the Google Graveyard but for dumb Intel acquisitions?

CRIU can use two mechanisms to detect page changes. One is the soft-dirty kernel feature which is mainlined and can be accessed via /proc/PID/pagemap [1]. The other is userfaultfd which is only partially merged in the newest kernel. userfaultfd lacks write detection which the article mentioned. My understanding is that using pagemap requires the entire process to be frozen while it is scanned for memory changes and the memory is copied while uffd allows for a more streaming/on-demand approach that doesn't require stopping the entire process.

[1] https://www.kernel.org/doc/Documentation/vm/soft-dirty.txt

VcXsrv doesn't work well with HDPI scaling which this claims to support out of the box.

Does this apply to Red Pro drives too?

My understanding of this product is that it is a revisiting of Very Long Instruction Word (VLIW) as seen in Itanium 20 years ago. I think that the idea of VLIW was a good idea that failed at the time due to the pure momentum of x86 and Moore's law.

Now the Moore's is basically at its end and x86 is partially stagnating, at least from Intel, other platforms like ARM are gaining traction and it seems like a good time to revisit VLIW.

I think another key factor is that most applications now run on top of platforms/frameworks rather than at the native level. This means you only need to port Linux, the JVM, node, python, and a few others and you captured a pretty large potential audience. Compare this to the mid 00's when moving to Itanium meant porting all you native apps.

It's not legal. They are hoping that people will be chill given the circumstances. Controlled digital lending has to match the model of a library/video rental stores where you borrow/rent something for a few days then return it. Even if you are not actively using the App/Website, which is easily detectable, they cannot return the item to their digital pool while you have it checked out.

Companies have tried to create Just In Time (JIT) media services that return digital items to a pool when you are not actively using them. This essentially creates micro loans with a time span of minutes to hours.

I can't remember the name of the company that was attempting this but they were shutdown due to a copyright lawsuit.

EDIT: They actually mention the company in the FAQ. ReDigi lost their lawsuit [1].

[1] http://www.ca2.uscourts.gov/decisions/isysquery/68b0f5b0-959...

This doesn't really track with Agricultural futures. They are all down in the last few months [1]. Either this is bait for retail investors or the pros are asleep at the wheel.

[1] https://www.cmegroup.com/trading/agricultural/

I just sent up an LXC container in 10 minutes to do GPU folding. Docker is much easier than LCX to configure, especially for GPU stuff. Really isn't that difficult. It's a single deb package.

There appears to be GPU based WUs available. I have been unable to get any CPU based WUs at all this week but I am currently working on some GPU WUs.

I think the demise of Lytro was a huge missed opportunity for the film industry. They had this and a number of other features in their cinema camera before they became defunct a few years ago.

https://www.youtube.com/watch?v=4qXE4sA-hLQ

TCS, Wipro, etc. probably skew this but it seems true to some extent at least in the bay area. [1]

[1] https://www.newsweek.com/h-1b-visa-row-foreign-workers-make-...

#5 is disputable.

It's called SYCL and no one uses it. It's been around since 2014.

Assuming Nintendo pressured Amazon by threatening to remove its first party sales from Amazon it's likely that this would be tortious interference with a contract. However since most of the third party sellers are selling a high volume of bootlegs like the article says it's unlikely they would sue for fear of a counter-claim of copyright infringement. Also the cost to sue probably outweighs the value of theses "businesses".

Prior art exists. This is already invalid. Just needs to go to court first.

CUDA has two APIs:

1. The runtime api (libcudart.so)

2. The driver api (libcuda.so).

The driver api is very close to the opencl api and is very low level. Most people use the CUDA runtime api which is vastly more convenient. The main difficulty with OpenCl and the driver api is that you have to manually load GPU code onto the device which then returns a handle. You generally have to load the code onto every device which means multiple handles for the same function. This makes executing kernel quiet a lot of work. The runtime api does this all automatically which make programming with CUDA quiet easy since launching a kernel is basically a function call. The CUDA rutime also automatically handles context creation which is another time saver.

When I first learned OpenCL I was shocked at how difficult is was to simply write a simple vector add program since there was all this additional code loading, creating contexts, etc. The setup / boiler plate was greater than the actually code itself.

It basically boils down to convenience in my opinion. Couple this with the fact the NVIDIA generally has the most powerful and energy efficient cards and it's no surprise they took the market.

You're presenting a false dichotomy. If people are being gouged then you can pass laws to limit that. You don't need single payer to solve these issues. Everyone knows the pricing system is BS. If that's the case then we should pass laws to change this.

Except you often have to wait weeks for non-life threatening issues. In the US you can get imaging done same or next day.

And yet when a pipeline was proposed it was quickly shot down [1].

[1] https://en.wikipedia.org/wiki/Energy_East

ADDENDUM: The amount of rail accidents in Canada is shockingly high. Multiple per day [2].

[2] http://www.bst-tsb.gc.ca/eng/stats/rail/2018/sser-ssro-2018....

If you haven't seen it all ready just take a look at the infamous "Let's Go Whaling!" talk here [1]. They're not even hiding the fact the these are the type of people Free2Play/Pay2Win games prey on anymore.

[1]. https://www.youtube.com/watch?v=xNjI03CGkb4

Dual port 100 and 200 Gbit/s network adapters.

You can use [1] from Intel to successfully intercept all syscalls from a given library, by default libc only. This library actually works by disassembling libc and replacing all `syscall` instructions with a jump to a global intercept function that you can write yourself. Incidentally it's also an LD_PRELOADed library.

[1] https://github.com/pmem/syscall_intercept

For those wondering I found this on WebMD.

> In 2000, the first long-acting synthetic insulin was approved by the U.S. Food and Drug Administration.

Looks like it will still be at least another year before a viable generic enters the market.