All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eddie Kohler <kohler@cs.ucla.edu>
To: dccp@vger.kernel.org
Subject: Re: CCID2: Tell DCCP to quickly check whether cwnd is available
Date: Fri, 22 Sep 2006 04:11:49 +0000	[thread overview]
Message-ID: <45136285.2070301@cs.ucla.edu> (raw)
In-Reply-To: <200609210930.21903@strip-the-willow>

Hi, a short note;

Andrea Bittau wrote:
> On Thu, Sep 21, 2006 at 09:30:21AM +0100, Gerrit Renker wrote:
>>  1/ TX Buffering: set size of TX ring buffer via socket option.
> 
> The size of the TX buffer is interesting in applications which want to do their
> own queue management.  That is, real-time applications that would prefer
> dropping certain packets and re-order other packets based on the state of the
> session.  We are used to the standard UNIX "push" model where you shove stuff in
> the kernel via write.  Perhaps a different architecture would be for the TX
> buffer to be in user-land and the kernel to pull from it.  There is a lot of
> overhead [context-switch] added, but there might be a good way of coding this.
> By doing so, the application chooses exactly what to send and when.  Perhaps
> this is equivalent to a 0 TX buffer size.

Junwen Lai and I designed and built an API very much like this --  a transmit 
ring in user space.  Gerrit referred to the paper.  It's actually similar to 
the design Xen uses for its virtual network drivers.

Eddie

  parent reply	other threads:[~2006-09-22  4:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21  8:30 CCID2: Tell DCCP to quickly check whether cwnd is available Gerrit Renker
2006-09-21 12:20 ` Andrea Bittau
2006-09-22  0:15 ` Ian McDonald
2006-09-22  0:18 ` Ian McDonald
2006-09-22  4:11 ` Eddie Kohler [this message]
2006-09-25  9:03 ` Gerrit Renker
2006-09-25 17:58 ` Ian McDonald

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=45136285.2070301@cs.ucla.edu \
    --to=kohler@cs.ucla.edu \
    --cc=dccp@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.