From: Andi Kleen <ak@suse.de>
To: Ganesan Rajagopal <rganesan@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Van Jacobson Channels - Earlier Work
Date: 17 May 2006 15:55:59 +0200 [thread overview]
Message-ID: <p737j4k4uxc.fsf@bragg.suse.de> (raw)
In-Reply-To: <xkvhves495x9.fsf@grajagop-lnx.cisco.com>
Ganesan Rajagopal <rganesan@debian.org> writes:
> Hi,
>
> A colleague at work pointed me to a 10 year old paper OSDI paper called Lazy
> Receiver Processing (See http://www.cs.rice.edu/CS/Systems/LRP/). The work
> appears similar to what Van Jacobson is proposing in his paper.
Linux has been implementing user context UDP/TCP (which is afaik the main core
feature of LRP) for many years now. netchannels has much more ideas though.
-Andi
prev parent reply other threads:[~2006-05-17 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 12:44 Van Jacobson Channels - Earlier Work Ganesan Rajagopal
2006-05-17 13:55 ` Andi Kleen [this message]
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=p737j4k4uxc.fsf@bragg.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rganesan@debian.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