William Martin williammartin

## iptables-regression.md

      
              3 files
            
          
              0 forks
            
          
              0 comments
            
          
              3 stars
            
          
                williammartin
                / iptables-regression.md
            
            
              Last active
              August 11, 2020 19:09
            
              
                iptables regression
              
          
    Iptables Regression Overview

We have encountered what appears to be a regression in iptables performance when appending many rules sequentially.
We believe we have narrowed the regression to this but do not understand the implications of this commit.
Summary provided below but more info available on this tracker story
Reproduction (credit @rosenhouse)

Set up


## iptables-regression-verification.md

      
              2 files
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                williammartin
                / iptables-regression-verification.md
            
            
              Last active
              January 13, 2017 11:47
            
              
                iptables regression patch verification
              
          
    Objective

To verify whether the iptables regression patches improve performance for both direct iptables executions and for garden NetOut API calls.
iptables rule addition

4.2 kernel


## pprof-guardian.sh
cd /usr/local/
wget "https://storage.googleapis.com/golang/go1.7.1.linux-amd64.tar.gz"
tar -zxf go1.7.1.linux-amd64.tar.gz
rm go1.7.1.linux-amd64.tar.gz
cd
mkdir go
cd go
mkdir src pkg bin
cd ../

## flake.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                williammartin
                / flake.md
            
            
              Created
              June 7, 2017 10:54
            
              
                Networking Flakiness in GATS
              
          
    Networking Flakiness in GATS

Description

When running nested GATS, we occasionally get containers without network connectivity.
It's unclear whether this is new flakiness. It's unclear whether this affects BOSH deployments.
The tests that seem to hit this the most are those in networking_test.go around resolving DNS, but DNS resolution is failing
due to a lack of connectivity (unable to ping 8.8.8.8) rather than a problem with resolution.

  
## subreaper.go
package subreaper

import (
	"unsafe"

	"golang.org/x/sys/unix"
)

func Set() error {
	return unix.Prctl(unix.PR_SET_CHILD_SUBREAPER, uintptr(1), 0, 0, 0)

## main.go
package main

import (
  "fmt"
  "os"
  "os/exec"
  "time"

  "github.com/williammartin/subreaper"
)

## subreaper_reaping_main.go
package main

import (
  "fmt"
  "os"
  "os/exec"
  "os/signal"
  "time"

  "github.com/williammartin/subreaper"

## no_matcher.go
package matcher_test

import (
	"os/exec"
	"time"

	. "github.com/onsi/ginkgo"
	. "github.com/onsi/gomega"
	"golang.org/x/sys/unix"
)

## matcher.go
func BeARunningProcess() types.GomegaMatcher {
	return &BeARunningProcessMatcher{}
}

type BeARunningProcessMatcher struct {
	actualPid int
}

func (matcher *BeARunningProcessMatcher) Match(actual interface{}) (bool, error) {
	pid, ok := actual.(int)

## acceptance_test.go
package acceptance_test

import (
	"os/exec"

	. "github.com/onsi/ginkgo"
	. "github.com/onsi/gomega"
	"github.com/onsi/gomega/gbytes"
	"github.com/onsi/gomega/gexec"
)
	cd /usr/local/
	wget "https://storage.googleapis.com/golang/go1.7.1.linux-amd64.tar.gz"
	tar -zxf go1.7.1.linux-amd64.tar.gz
	rm go1.7.1.linux-amd64.tar.gz
	cd
	mkdir go
	cd go
	mkdir src pkg bin
	cd ../
	package subreaper

	import (
	"unsafe"

	"golang.org/x/sys/unix"
	)

	func Set() error {
	return unix.Prctl(unix.PR_SET_CHILD_SUBREAPER, uintptr(1), 0, 0, 0)
	package main

	import (
	"fmt"
	"os"
	"os/exec"
	"time"

	"github.com/williammartin/subreaper"
	)
	package matcher_test

	import (
	"os/exec"
	"time"

	. "github.com/onsi/ginkgo"
	. "github.com/onsi/gomega"
	"golang.org/x/sys/unix"
	)
	func BeARunningProcess() types.GomegaMatcher {
	return &BeARunningProcessMatcher{}
	}

	type BeARunningProcessMatcher struct {
	actualPid int
	}

	func (matcher *BeARunningProcessMatcher) Match(actual interface{}) (bool, error) {
	pid, ok := actual.(int)
	package acceptance_test

	import (
	"os/exec"

	. "github.com/onsi/ginkgo"
	. "github.com/onsi/gomega"
	"github.com/onsi/gomega/gbytes"
	"github.com/onsi/gomega/gexec"
	)