search for: metatdata

...wrote: > Hi Michael, > > This is cool stuff, thanks for sharing! > > On 06/15/2017 11:51 AM, Michael Spencer via llvm-dev wrote: > >> The first is a new llvm pass which uses branch frequency info to get >> counts for each call instruction and then adds a module flags metatdata >> table of function -> function edges along with their counts. >> >> The second takes the module flags metadata and writes it into a >> .note.llvm.callgraph section in the object file. This currently just dumps >> it as text, but could save space by reusing the str...

...over standard PGO with zero cases of slowdowns and up to 15% > reduction in ITLB misses. > > > There are three parts to this implementation. > > The first is a new llvm pass which uses branch frequency info to get counts > for each call instruction and then adds a module flags metatdata table of > function -> function edges along with their counts. > > The second takes the module flags metadata and writes it into a > .note.llvm.callgraph section in the object file. This currently just dumps > it as text, but could save space by reusing the string table. > >...

...0% to 5% performance improvement over standard PGO with zero cases of slowdowns and up to 15% reduction in ITLB misses. There are three parts to this implementation. The first is a new llvm pass which uses branch frequency info to get counts for each call instruction and then adds a module flags metatdata table of function -> function edges along with their counts. The second takes the module flags metadata and writes it into a .note.llvm.callgraph section in the object file. This currently just dumps it as text, but could save space by reusing the string table. The last part is in lld. It read...

...is cool stuff, thanks for sharing! >>> >>> On 06/15/2017 11:51 AM, Michael Spencer via llvm-dev wrote: >>> >>>> The first is a new llvm pass which uses branch frequency info to get >>>> counts for each call instruction and then adds a module flags metatdata >>>> table of function -> function edges along with their counts. >>>> >>>> The second takes the module flags metadata and writes it into a >>>> .note.llvm.callgraph section in the object file. This currently just dumps >>>> it as text,...

...>>>> >>>>> On 06/15/2017 11:51 AM, Michael Spencer via llvm-dev wrote: >>>>> >>>>>> The first is a new llvm pass which uses branch frequency info to get >>>>>> counts for each call instruction and then adds a module flags metatdata >>>>>> table of function -> function edges along with their counts. >>>>>> >>>>>> The second takes the module flags metadata and writes it into a >>>>>> .note.llvm.callgraph section in the object file. This currently just du...

Hello I'm using Samba 4.0.1 also to authenticate users via Kerberos. Once in a while however I have to regenerate a keytab, because for reasons unknown to me, the KVNO is increased by one. I'm not doing anything with an account the SPN is bound to. The KVNO seems to change automagically after few days and service cannot talk to the KDC unless I create a new keytab. What can cause the

...esirable. * The implication that a hypervisor ought to be providing a unbounded stream of random numbers, rather than a fixed amount of seed. I think the most obvious approach would be to provide the VM, at startup, with a page containing a fixed amount of random number seed, along with some metatdata. Some platform-specific way of discovering the location of the page would have to be defined. (That might an MSR but more likely it would be Device Tree or ACPI.) After the guest has read the page, it would be free to treat it as normal memory. The metadata need do little more than specify the...

Hello :) I am looking around __builtin_expect() directive for optimization. ( http://llvm.org/docs/BranchWeightMetadata.html ) Since it is not included in v2.9, I am searching about it on svn trunk. I found that the lowering phase generates branch-weight metadata node for that directive. However, I can't find any code related to the metadata even in the branch transformation code. IMHO, in

...ism. Given that, the length of the stream is largely irrelevant, except that an unbounded stream allowed reseeding after boot. > > I think the most obvious approach would be to provide the VM, at > startup, with a page containing a fixed amount of random number seed, > along with some metatdata. > > Some platform-specific way of discovering the location of the page > would have to be defined. (That might an MSR but more likely it would > be Device Tree or ACPI.) > > After the guest has read the page, it would be free to treat it as > normal memory. > > The meta...

...ism. Given that, the length of the stream is largely irrelevant, except that an unbounded stream allowed reseeding after boot. > > I think the most obvious approach would be to provide the VM, at > startup, with a page containing a fixed amount of random number seed, > along with some metatdata. > > Some platform-specific way of discovering the location of the page > would have to be defined. (That might an MSR but more likely it would > be Device Tree or ACPI.) > > After the guest has read the page, it would be free to treat it as > normal memory. > > The meta...

I bumped the logging up. samba-tool domain level raise --domain-level=2008_R2 schema_fsmo_init: we are master[yes] updates allowed[no] schema_fsmo_init: we are master[yes] updates allowed[no] The updates_allowed[no] concerns me? On Fri, Jul 8, 2016 at 9:45 AM, Jason Waters <jason at geeknocity.com> wrote: > I'm pretty sure the domain level raise is failing on this system.

When you say “real symlinks on OSX” do you mean an “alias” that Finder would create? Or a Unix-type symlink using the “ ln -s file link” command in Terminal? A Finder alias is not the same as a Unix-type symlink. My NAS runs Debian Linux with version 4.3.11 of smbd; my clients are all OSX Mojave. If I create an alias using Finder on the NAS, it behaves like a normal alias in OSX UNLESS I move

On 01/11/2016 3:05 pm, Laine Stump wrote: > On 01/11/2016 02:25 PM, Andre Goree wrote: >> >> I have some questions regarding the way that networking is handled via >> qemu/kvm+libvirt -- my apologies in advance if this is not the proper >> mailing list for such a question. >> >> >> I am trying to determine how exactly I can manipulate traffic from

Here's a draft CommonHV spec. It's also on github: https://github.com/amluto/CommonHV So far, this provides a two-way RNG interface, a way to detect it, and a way to detect other hypervisor leaves. The latter is because, after both the enormous public thread and some private discussions, it seems that detection of existing CPUID paravirt leaves is annoying and inefficient. If

Here's a draft CommonHV spec. It's also on github: https://github.com/amluto/CommonHV So far, this provides a two-way RNG interface, a way to detect it, and a way to detect other hypervisor leaves. The latter is because, after both the enormous public thread and some private discussions, it seems that detection of existing CPUID paravirt leaves is annoying and inefficient. If

A month or two ago I sent an email to this list proposing to expand the list of "standard" tags for Ogg Vorbis. No tag would be required, but if you wanted to encode certain types of information about a file, you could use a standard tag. I went through the whole discussion, and revised my proposal in light of all the comments from everyone. Here is the updated proposal. This

After running ceph on XFS for some time, I decided to try btrfs again. Performance with the current "for-linux-min" branch and big metadata is much better. The only problem (?) I''m still seeing is a warning that seems to occur from time to time: [87703.784552] ------------[ cut here ]------------ [87703.789759] WARNING: at fs/btrfs/inode.c:2103