similar to: dumping using tftp

Displaying 20 results from an estimated 1000 matches similar to: "dumping using tftp"

2014 Oct 10
1
dumping using tftp
Hi Yeah I ended up figuring it out My usage for the tool will be to gather hardware specs of new servers that we receive and servers we have in storage I will then see if I can script something to phrase the dumps to update our inventory tool. Our main issue is that gathering information manually by opening the server and having to locate each parts is time consuming and being humans we are
2014 Oct 10
0
dumping using tftp
I'm not sure to get your point properly. If you need to upload a result to a tftp server, you need to PXE boot hdt to gain the network service. HDT can be booted in PXE by using the hdt.c32 which is available with every syslinux release. Does it make much more meaning ? I also would be very interesting on what is your usage of HDT and expectations ;o) Erwan, 2014-10-09 19:19 GMT+02:00
2014 Oct 24
0
Only 1 physical CPU is seen
Hello Is there a way from using HDT to determine the correct number of physical CPU's in the system with their correct amount of cores? It seems HDT is only displaying 1 CPU and is sorta combining the cores. Even when going through the dump files, I'm not able to use the data to correctly determine how many CPU's are in the system. Is there away? - Philippe Johnston IT-GNS -
2019 Feb 25
2
Making LLD PDB generation faster
Yes, -Tllvm works. [cid:image002.jpg at 01D4CCF6.C440CFF0] From: Zachary Turner <zturner at google.com> Sent: Monday, February 25, 2019 10:36 AM To: Leonardo Santagada <santagada at gmail.com> Cc: Alexandre Ganea <alexandre.ganea at ubisoft.com>; Reid Kleckner <rnk at google.com>; llvm-dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] Making LLD PDB
2019 Feb 27
4
Making LLD PDB generation faster
This could be ICF. There were lots of issues with ICF on ARM64, but they are not inherently ARM64-specific, they just come up there more often. See https://reviews.llvm.org/D56986 which fixes that. Easiest thing is always to profile or add /time to see what's slow. On Wed, Feb 27, 2019 at 6:30 AM Leonardo Santagada <santagada at gmail.com> wrote: > Anyone would know why lld takes
2019 Feb 25
3
Making LLD PDB generation faster
Can you please try using Ninja instead? cmake -G Ninja f:/svn/llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_OPTIMIZED_TABLEGEN=true -DLLVM_EXTERNAL_LLD_SOURCE_DIR=f:/svn/lld -DLLVM_TOOL_LLD_BUILD=true -DLLVM_ENABLE_LLD=true -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DCMAKE_LINKER="C:/Program
2019 Feb 25
2
Making LLD PDB generation faster
I think its a huge bug that it doesn't raise any errors or warnings about it. But I will open a ticket on cmake, they should be using clang-cl.exe and lld-link.exe if T="llvm" probably set host to 64 bit as well. On Mon, Feb 25, 2019 at 3:34 PM Zachary Turner <zturner at google.com> wrote: > > I don’t think changing the compiler or linker is supported with the vs
2019 Feb 25
5
Making LLD PDB generation faster
Times for lld compiled with LTO: Input File Reading: 1430 ms ( 3.3%) Code Layout: 486 ms ( 1.1%) PDB Emission (Cumulative): 41042 ms ( 94.6%) Add Objects: 33117 ms ( 76.4%) Type Merging: 25861 ms ( 59.6%) Symbol Merging: 7011 ms ( 16.2%) TPI Stream Layout: 996 ms ( 2.3%) Globals Stream Layout:
2019 Feb 25
2
Making LLD PDB generation faster
Sadly the patch on https://reviews.llvm.org/D55585 didn't apply on my clone of llvm at all :( It will take me quite some time to test this out. On Mon, Feb 25, 2019 at 5:08 PM Alexandre Ganea <alexandre.ganea at ubisoft.com> wrote: > > For enabling large memory pages, see this link: https://support.sisoftware.co.uk/knowledgebase.php?article=52 > > Meow hash isn't in the
2005 Jan 17
1
Re: Any interest in a Canadian Asterisk
Quoting asterisk-users-request@lists.digium.com: > > Would it be considered trolling to start a thread on Cleaning Maple > > Syrup off of Dial Pads, or Wiring your Moose for Wi-Fi? > > Let's not forget the weekly "tooques and telephony" segment, and a > review of > the best block heaters for your wi-fi fones. > Oh, we're gonna have a good time next
2019 Feb 28
3
Making LLD PDB generation faster
As for multithreaded ghashes: Even if the hashtable stores 32-bit indices to SeenHashes, you would still need to compare the ghashes for collisions: https://github.com/llvm/llvm-project/blob/master/llvm/include/llvm/ADT/DenseMap.h#L627 Finding the 32-bit index in the hashtable doesn’t necessarily mean it’s the right one. The following table shows the collision distribution when inserting (type)
2019 Feb 25
2
Making LLD PDB generation faster
That's good news. For having debug info, you could try adding /Z7 on the cmake cmd-line, such as -DCMAKE_CXX_FLAGS="/Z7". Or use the 'RelWithDebInfo' target instead of 'Release' and add -DCMAKE_CXX_FLAGS="/Ob2" (because that target uses /Ob1 as a default). Can you please send a patch on Phabricator if you fix the LLVM_ENABLE_PDB issue with Clang? The goal
2019 Feb 25
4
Making LLD PDB generation faster
How do you compile LLD? There's a big difference between when using MSVC vs Clang. The parallel ghash patch I was mentioning is almost 2x as fast when using Clang 7.0+ vs. MSVC 15.9+, I don't know exactly why. I also suggest you use the Release target. You should also grab this patch: https://reviews.llvm.org/D55056 - I had to revert it because it was causing issues with LLDB. But it
2023 Jan 30
11
[p2v PATCH 00/11] Expose virt-v2v's "-oo"; re-enable openstack
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1792141 Let the user pass "-oo" options from the kernel cmdline and from the GUI to virt-v2v. This is primarily useful with the OpenStack output mode, so reenable that mode. Cc: Alban Lecorps <alban.lecorps at ubisoft.com> Laszlo Alban Lecorps (1): Introduce "p2v.output.misc" for passing "-oo" options
2009 Apr 05
4
Game install failed
Hello, tried to install Brothers In Arms: Earned In Blood in Hardy, Wine 1.1.18, and it gets through the entire install, then asks me to reboot. When i click yes, the window disappears. But nothing happens. I open it again to find the same prompt right in front of my face. I've tried wineboot in the Terminal, tried even restarting ubuntu itself. But it always comes up with that same
2020 Jul 03
4
[cfe-dev] RFC: Replacing the default CRT allocator on Windows
Thanks for the suggestion James, it reduces the commit by about ~900 MB (14,9 GB -> 14 GB). Unfortunately it does not solve the performance problem. The heap is global to the application and thread-safe, so every malloc/free locks it, which evidently doesn’t scale. We could manually create thread-local heaps, but I didn’t want to go there. Ultimately allocated blocks need to share ownership
2020 Apr 10
4
Running clang tests
Hi, I’d just like to interject to say that building within Visual Studio isn’t really that bad. Running the lit tests is a bit painful because the LLVM build tools that are integrated with the build system don’t play nice with msbuild. Particularly, I’ve never been able to actually cancel an invocation of lit or tablegen via visual studio. That said, there is a huge upside to building with
2020 Apr 01
2
LLD issue on a massively parallel build machine
On another login node which is 256 (GB)/48 (nodes) JURECA at JSC, I never had an LLD issue without setting -j when executing ninja in the past few weeks. On Thu, Apr 2, 2020 at 7:17 AM Itaru Kitayama <itaru.kitayama at gmail.com> wrote: > Tom, > Then what ratio do you think it’s minimal? > > On Thu, Apr 2, 2020 at 6:11 Tom Stellard <tstellar at redhat.com> wrote: >
2006 Feb 22
3
How to make a symlink appear as a real file (for a Linux client)?
I have a share with a couple of symlinked files in it. On a Samba server, it looks like this for "addon" directory: # ls -l (...) acrobatreader7 (...) addon -> /home/samba/unattended-write/packages Now, if I mount it on a Linux client using smbmount, symlinks point to non existing directories locally (/home/samba/unattended-write/packages exist only on a Samba server): #
2019 Feb 24
2
Making LLD PDB generation faster
Leonardo, to answer to your questions, yes to all of them  You can take a look at this prototype/proposal: https://reviews.llvm.org/D55585 Overall, computing ghashes in parallel at link-time and merging Types with them is less costly that the current approach to merging. The 35sec you’re seeing for merging should go down to about 15sec. The patch doesn’t parallelize (yet) the Type merging