Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ice799
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
Dynamic Linking: ELF vs. Mach-O
(timetobleed.com)
62 points
by
ice799
16y ago
|
0 comments
32.
▲
by
ice799
16y ago
a couple months working in our spare time after work/weekends.
33.
▲
by
ice799
17y ago
This. I built this because I like working on this sort of thing and because it lowers the bar for everyone else who doesn't know how to or want to rebuild their binaries. Also, depends a lot on your infrastructure. Sometimes it's easier to
34.
▲
by
ice799
17y ago
I didn't hardcode any addresses. That's why it works on so many different Ruby builds.
35.
▲
Descent into Darkness: Understanding your system’s ABI is the only way out
(timetobleed.com)
54 points
by
ice799
17y ago
|
21 comments
36.
▲
by
ice799
17y ago
thanks, glad you liked the slides.
37.
▲
by
ice799
17y ago
working on it.
38.
▲
by
ice799
17y ago
yup, it was recorded. not sure when the video will be out, but i'll tweet it or something as soon as i hear.
39.
▲
by
ice799
17y ago
glad you liked the slides.
40.
▲
Memprof: A Ruby level memory profiler
(timetobleed.com)
70 points
by
ice799
17y ago
|
3 comments
41.
▲
Hot patching inlined functions with x86_64 asm metaprogramming
(timetobleed.com)
7 points
by
ice799
17y ago
|
0 comments
42.
▲
Rewrite your Ruby VM at runtime to hot patch useful features
(timetobleed.com)
24 points
by
ice799
17y ago
|
10 comments
43.
▲
Defeating the Matasano C++ Challenge with ASLR enabled
(timetobleed.com)
23 points
by
ice799
17y ago
|
0 comments
44.
▲
by
ice799
17y ago
Fun challenge! I wonder when the contest closes? I'd like to blog about my solution. Hopefully my email to matasano doesn't get eaten by a spam filter :/
45.
▲
Extending ltrace to make your Ruby/Python/Perl/PHP apps faster
(timetobleed.com)
61 points
by
ice799
17y ago
|
8 comments
46.
▲
by
ice799
17y ago
Firstly - thanks for reading the blog post. Some of the things mentioned help to reduce CPU usage so that the CPU can do more useful things (TSO, IOAT, DCA, NIC irqs, etc). ioat moves a surprising number of bytes for the CPU. You might be
47.
▲
by
ice799
17y ago
Indeed - but flipping the "DCA on" switch in the BIOS sets the bits in these registers. So it is different, but it does the same thing.
48.
▲
Enabling BIOS options on a live server with no rebooting
(timetobleed.com)
23 points
by
ice799
17y ago
|
2 comments
49.
▲
by
ice799
17y ago
I think the way most people get started is to build simple C programs, and then use objdump to try and understand the output of the compiler (use -O0, of course =) The intel CPU manuals have a lot of the low-level systems information about
50.
▲
by
ice799
17y ago
correct. but they each take a global interpreter lock ensuring only one is executing at any given time.
51.
▲
by
ice799
17y ago
Hi. Author here. Ruby 1.9 uses libpthread which creates stacks for its threads in a similar way (mmap and a guard page).
52.
▲
by
ice799
17y ago
timetobleed guy here - I'm a CMU CS alumn (class of '07). I miss the good old days of 213 and 410 =]
53.
▲
Yo Dawg: Using a package management system to install a package management system
(timetobleed.com)
13 points
by
ice799
17y ago
|
5 comments
54.
▲
by
ice799
17y ago
I tried with a FF3 on OSX and then in a VM with IE8 - got two different prices.
55.
▲
by
ice799
17y ago
Awesome.
56.
▲
Things You Don’t Know About User IDs That Will Destroy You
(timetobleed.com)
69 points
by
ice799
17y ago
|
16 comments
57.
▲
by
ice799
18y ago
Good call. I should have included something like this in my post. I'll update it and give you a shout-out. Thanks for commenting!
58.
▲
MySQL Doesn’t Always Suck; This Time it’s AMD
(timetobleed.com)
63 points
by
ice799
18y ago
|
12 comments
59.
▲
by
ice799
18y ago
You might be reading the article too literally -- you can test more than just tcmalloc, of course (ned, ptmalloc*, libumem, etc). It is -very- possible that one of these allocators will handle our memory footprint more gracefully than say,
60.
▲
by
ice799
18y ago
Short answer: depends what you care about. Long answer: if the allocator is poorly designed, a lot of time will be spent traversing its free list/tree/whatever looking for a block to fit your size requirements. this lookup time can be exac
More ›