From: Benjamin LaHaise <bcrl@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Brian Raymond <braymond@fvc.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Async UDP I/O?
Date: Mon, 26 Nov 2001 17:01:05 -0500 [thread overview]
Message-ID: <20011126170105.A15582@redhat.com> (raw)
In-Reply-To: <6A5AF4EA59EB214BB0267741CE2C86EF0E07F5@neptune.cuseeme.com> <E168TX1-00070O-00@the-village.bc.nu>
In-Reply-To: <E168TX1-00070O-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Nov 26, 2001 at 09:43:15PM +0000
On Mon, Nov 26, 2001 at 09:43:15PM +0000, Alan Cox wrote:
> What do you mean by "asynchronous UDP" - all UDP is asynchronous. You ask
> it to send it and it gets queued or dropped somewhere - its not subject
> to flow control like TCP
>
> Can you explain more ?
Async receive helps a lot when you've got tons of open sockets (needed to
get queuing right). I think that the current tx mechanism is broken; it's
quite useful to get backpressure from network devices for things like mlppp
implemented the right way (as a network protocol, instead of its own layer).
-ben
prev parent reply other threads:[~2001-11-26 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 21:07 Brian Raymond
2001-11-26 21:43 ` Alan Cox
2001-11-26 22:01 ` Benjamin LaHaise [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=20011126170105.A15582@redhat.com \
--to=bcrl@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=braymond@fvc.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®