Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Mar 2018 00:41:58 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 226649] [NEW PORT] benchmarks/uperf: Network performance tool to model and replay of networking patterns
Message-ID:  <bug-226649-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226649

            Bug ID: 226649
           Summary: [NEW PORT] benchmarks/uperf: Network performance tool
                    to model and replay of networking patterns
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs@FreeBSD.org
          Reporter: 0mp@FreeBSD.org
 Attachment #191540 text/plain
         mime type:

Created attachment 191540
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D191540&action=
=3Dedit
Shell archive of a new uperf port (version: v1.0.6.20180221)

Uperf is a network performance measurement tool that supports execution of
workload profiles. It was requested by gnn@.

This piece of software feels a little bit unmaintained. That's why I've dec=
ided
to check out the newest version available from the upstream tree
(v1.0.6.20180221, which is slightly newer than the latest v1.0.6 release

I've attached an initial version of the port. I'll probably have to improve=
 it
here and there but the core should be fine. After all, it passes my QA test=
s.

I kindly ask for a review and suggestions :)

---

QA:
 * poudriere: 11.1-RELEASE (amd64, i386), 12.0-CURRENT (amd64), 10.4-RELEASE
(amd64)
 * portlint
 * FreeBSD 12.0-CURRENT r330529 amd64

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-226649-13>