We announced with Intel back in November that we would be getting early access to Skylake [1]. Today's announcement is that we're ready to let more people in the door.
E3 is not a server SKU, it's meant for workstations and it's more similar to i7 than E5. It lacks various features including ECC RAM which, I suppose, is a no-starter for cloud hosting. Also some virtualization capabilities are missing, notably accelerated interrupt injection (APICv+posted interrupts).
I think it's relying on libcrypto from openssl, at least that was the case when it came out. E.g. it implements TLS/SSL protocols only, no crypto. Not sure if that's changed and they implemented crypto as well.
It's pretty much the definition of false economy. Would you rather save a few cycles or suffer debilitating security bugs at random intervals? Always use calloc unless a) there's a proven performance problem and b) you know for a fact that due to careful inspection/static analysis/black magic malloc is safe. Then use calloc anyway because why risk it?
It depends on the size of the chunk of allocated memory. If it is quite large, time spent zeroing it can be substantial.
Then again, if you're allocating in performance critical path, you're doing it wrong anyways.
Is this true? I thought that the salary of H1b worker must match an average paid for this kind of position in this area. In fact, I'm fairly certain that the company sponsoring H1B must supply documents showing they did the research, on both wages and the fact that they couldn't find anyone in the US to do this kind of work.
From what I've seen at my employer, H1Bs end up getting paid less simply due having a different set of priorities. We don't discriminate between citizens and H1Bs when crafting an offer for employment, but citizens are far more likely to try to negotiate for more compensation whereas H1Bs are more interested in getting an EB2 and are even willing to sacrifice salary to get that.
It wasn't until I hired a few H1Bs that I understood that the H1B discount isn't just a simple wrong. When looking at H1B compensation, we should probably also include additional legal fees paid on behalf of the worker rather than simply comparing salary to salary if we want an apples-to-apples comparison.
this is seems to be an offshoot/extension of pf-ring.
apart from performing packet operations in userland also defines a language with functional-composition (take a packet, return an 'enriched' packet) for further processing e.g. fanout/io etc.
ast from pfq/lang application gets translated into appropriate structures, in the kernel, and gets executed on top of the driver...
