netdev - Blogpost: Explaining why I do PPS measurement with 64 bytes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20140911111807.754b7336@redhat.com>
Date:	Thu, 11 Sep 2014 11:18:07 +0200
From:	Jesper Dangaard Brouer <brouer@...hat.com>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Cc:	brouer@...hat.com
Subject: Blogpost: Explaining why I do PPS measurement with 64 bytes

People generally seem to have a hardtime understanding why I'm using
64byte packets and measuring PPS, when tuning the network stack.
People keep telling me this is artificial benchmarking, which is true,
but there is another reason behind these measurements.

Which I have described in this blogpost:
 http://netoptimizer.blogspot.dk/2014/09/packet-per-sec-measurements-for.html

I'm basically leveraging the PPS measurements to deduct the nanosec
improvements I'm making to the code.

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Sr. Network Kernel Developer at Red Hat
  Author of http://www.iptv-analyzer.org
  LinkedIn: http://www.linkedin.com/in/brouer
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html