From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
Cc: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] sch_fq and sk->sk_pacing_rate
Date: Mon, 27 Apr 2015 17:15:43 +0200 [thread overview]
Message-ID: <20150427151543.GA10035@sesse.net> (raw)
In-Reply-To: <AE7F97DB5FEE054088D82E836BD15BE9319C3445@xmb-aln-x05.cisco.com>
On Mon, Apr 27, 2015 at 02:56:38PM +0000, Bill Ver Steeg (versteb) wrote:
> Oops- I seem to have hit send too quickly. I think setsockopt(sockfd,
> SOL_SOCKET, SO_MAX_PACING_RATE, &val, sizeof(val)) is the call I am looking
> for. I was looking on an older kernel when I wrote the first note.
>
> Comments still welcome on it use, though.
cubemap uses it. It works great.
/* Steinar */
--
Homepage: http://www.sesse.net/
next prev parent reply other threads:[~2015-04-27 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 14:56 Bill Ver Steeg (versteb)
2015-04-27 15:15 ` Steinar H. Gunderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-27 14:49 Bill Ver Steeg (versteb)
2015-04-27 15:30 ` Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150427151543.GA10035@sesse.net \
--to=sgunderson@bigfoot.com \
--cc=bloat@lists.bufferbloat.net \
--cc=versteb@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox