search for: 88s

...B to 2MBs from samba to winders whereas winders to winders does several times as fast It does not apear to be the hub or the network cards as the following indicates A 110MB file xferred from samba linux - linux takes about 77s doing the same over NFS takes 11s. I also did this with a 740MB iso 88s over nfs ~ 440 over smbfs ?? I get similar transfer rates when using the samba server on my pc. I have tested this also with a base smb.conf consisting only of - server name - workgroup name - share name - share path no noticeable difference the running kernel is a 2.6.9 cko2 network cards ini...

Dear all, I have a grid of 720 columns by 360 rows of global population density values, and hope to convert this to column format using the 'melt' command in the 'reshape' package. I'm not receiving any errors as such, but when the code has finished running, my output looks like this: > head(PopDens.long) Latitude Longitude PopDensity 1 -84.75 V1 0 2

.... It would be great to group our 3k obj debug information in groups so that this linking steps can be paralelizable. Is there any support maybe for merging pdb with pdb util and then feeding that to lld-link instead of .obj debug info? I also re-read the post about ghash and it says blink links in 88s, the 28s you talk about is with unrelased optimizations only? On Tue, Jan 30, 2018 at 5:54 AM, Zachary Turner <zturner at google.com> wrote: > You can make a PDB per lib (consider msvcrtd.pdb which ships with MSVC), > but all these per-lib PDBs would have to be merged into a single ma...

...g >> information in groups so that this linking steps can be paralelizable. Is >> there any support maybe for merging pdb with pdb util and then feeding that >> to lld-link instead of .obj debug info? >> >> I also re-read the post about ghash and it says blink links in 88s, the >> 28s you talk about is with unrelased optimizations only? >> >> On Tue, Jan 30, 2018 at 5:54 AM, Zachary Turner <zturner at google.com> >> wrote: >> >>> You can make a PDB per lib (consider msvcrtd.pdb which ships with MSVC), >>> but all...

...roup our 3k obj debug > information in groups so that this linking steps can be paralelizable. Is > there any support maybe for merging pdb with pdb util and then feeding that > to lld-link instead of .obj debug info? > > I also re-read the post about ghash and it says blink links in 88s, the > 28s you talk about is with unrelased optimizations only? > > On Tue, Jan 30, 2018 at 5:54 AM, Zachary Turner <zturner at google.com> > wrote: > >> You can make a PDB per lib (consider msvcrtd.pdb which ships with MSVC), >> but all these per-lib PDBs would hav...

...mation in groups so that this linking steps can be >>> paralelizable. Is there any support maybe for merging pdb with pdb util and >>> then feeding that to lld-link instead of .obj debug info? >>> >>> I also re-read the post about ghash and it says blink links in 88s, the >>> 28s you talk about is with unrelased optimizations only? >>> >>> On Tue, Jan 30, 2018 at 5:54 AM, Zachary Turner <zturner at google.com> >>> wrote: >>> >>>> You can make a PDB per lib (consider msvcrtd.pdb which ships with >...

...so that this linking steps can be paralelizable. >>>> Is there any support maybe for merging pdb with pdb util and then feeding >>>> that to lld-link instead of .obj debug info? >>>> >>>> I also re-read the post about ghash and it says blink links in 88s, the >>>> 28s you talk about is with unrelased optimizations only? >>>> >>>> On Tue, Jan 30, 2018 at 5:54 AM, Zachary Turner <zturner at google.com> >>>> wrote: >>>>> >>>>> You can make a PDB per lib (consider msvcr...

You can make a PDB per lib (consider msvcrtd.pdb which ships with MSVC), but all these per-lib PDBs would have to be merged into a single master PDB at the end, so you still can't avoid that final . In a way, that's similar to the idea behind /DEBUG:FASTLINK (keep the debug info in object files to eliminate the cost of merging types and symbol records) and we know what the problems with

...n be > paralelizable. > >>>> Is there any support maybe for merging pdb with pdb util and then > feeding > >>>> that to lld-link instead of .obj debug info? > >>>> > >>>> I also re-read the post about ghash and it says blink links in 88s, > the > >>>> 28s you talk about is with unrelased optimizations only? > >>>> > >>>> On Tue, Jan 30, 2018 at 5:54 AM, Zachary Turner <zturner at google.com> > >>>> wrote: > >>>>> > >>>>> You can...

...;>>> Is there any support maybe for merging pdb with pdb util and then >> >>>> feeding >> >>>> that to lld-link instead of .obj debug info? >> >>>> >> >>>> I also re-read the post about ghash and it says blink links in 88s, >> >>>> the >> >>>> 28s you talk about is with unrelased optimizations only? >> >>>> >> >>>> On Tue, Jan 30, 2018 at 5:54 AM, Zachary Turner <zturner at google.com> >> >>>> wrote: >> >>>&...

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking