netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Ronghua Zhang <rz5b@cs.virginia.edu>
Cc: kashyapv@us.ibm.com, shemminger@osdl.org, netdev@oss.sgi.com
Subject: Re: [PATCH] proportional share accept()
Date: Sun, 29 Feb 2004 22:05:13 -0800	[thread overview]
Message-ID: <20040229220513.68eed11f.davem@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.51.0402261659350.24561@mamba.cs.Virginia.EDU>

On Thu, 26 Feb 2004 17:08:23 -0500 (EST)
Ronghua Zhang <rz5b@cs.virginia.edu> wrote:

> www.cs.virginia.edu/~rz5b/research/kernel-qos.htm

I looked at this, it's basically netfilter TCP port rewriting
which knows about per-socket quotas and limits.

You could write this as a 10 line netfilter module, with zero
modifications to any of the core net/ipv4 TCP code at all.
And that's how I'd like to see something like this done.

Otherwise it looks like a nice way of doing this.

  parent reply	other threads:[~2004-03-01  6:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25 16:43 [PATCH] proportional share accept() Vivek Kashyap
2004-02-25 17:21 ` Stephen Hemminger
2004-02-25 18:12   ` David S. Miller
2004-02-25 19:07     ` kashyapv
2004-02-25 19:17       ` David S. Miller
2004-02-25 19:30         ` kashyapv
2004-02-26 22:08           ` Ronghua Zhang
2004-02-27 22:13             ` David S. Miller
2004-03-04 20:51               ` Vivek Kashyap
2004-03-04 21:52                 ` Ronghua Zhang
2004-03-01  6:05             ` David S. Miller [this message]
2004-03-01 10:11               ` Vivek Kashyap
     [not found]   ` <Pine.WNT.4.44.0402251101300.1572-100000@w-vkashyap95.des.sequent.com>
2004-02-25 20:03     ` Stephen Hemminger
2004-02-25 22:31       ` kashyapv
2004-02-26  2:35 ` James Morris

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040229220513.68eed11f.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=kashyapv@us.ibm.com \
    --cc=netdev@oss.sgi.com \
    --cc=rz5b@cs.virginia.edu \
    --cc=shemminger@osdl.org \
    /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;
as well as URLs for NNTP newsgroup(s).