Seth Wright Crosse

## fork-is-evil-vfork-is-good-afork-would-be-better.md

      
              1 file
            
          
              9 forks
            
          
              27 comments
            
          
              182 stars
            
          
                nicowilliams
                / fork-is-evil-vfork-is-good-afork-would-be-better.md
            
            
              Last active
              May 18, 2024 14:10
            
              
                fork() is evil; vfork() is goodness; afork() would be better; clone() is stupid
              
          
    I recently happened upon a very interesting implementation of popen() (different API, same idea) called popen-noshell using clone(2), and so I opened an issue requesting use of vfork(2) or posix_spawn() for portability.  It turns out that on Linux there's an important advantage to using clone(2).  I think I should capture the things I wrote there in a better place.  A gist, a blog, whatever.

This is not a paper.  I assume reader familiarity with fork() in particular and Unix in general, though, of course, I link to relevant wiki pages, so if the unfamiliar reader is willing to go down the rabbit hole, they should be able to come ou


## avx_sigh.md

      
              1 file
            
          
              3 forks
            
          
              0 comments
            
          
              66 stars
            
          
                rygorous
                / avx_sigh.md
            
            
              Last active
              June 1, 2024 02:05
            
          
why doesn't radfft support AVX on PC?

So there's two separate issues here: using instructions added in AVX and using 256-bit wide vectors. The former turns out to be much easier than the latter for our use case.
Problem number 1 was that you positively need to put AVX code in a separate file with different compiler settings (/arch:AVX for VC++, -mavx for GCC/Clang) that make all SSE code emitted also use VEX encoding, and at the time radfft was written there was no way in CDep to set compiler flags for just one file, just for the overall build.
[There's the GCC "target" annotations on individual funcs, which in principle fix this, but I ran into nasty problems with this for several compiler versions, and VC++ has no equivalent, so we're not currently using that and just sticking with different compilation units.]
The other issue is to do with CPU power management.

  
## youtube-search.py
#!/usr/bin/python3

# Copyright (C) 2020  Stefan Vargyas
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
	#!/usr/bin/python3

	# Copyright (C) 2020 Stefan Vargyas
	#
	# Permission is hereby granted, free of charge, to any person obtaining a copy
	# of this software and associated documentation files (the "Software"), to deal
	# in the Software without restriction, including without limitation the rights
	# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
	# copies of the Software, and to permit persons to whom the Software is
	# furnished to do so, subject to the following conditions: