From: Ian Molton <spyro@armlinux.org>
To: root@chaos.analogic.com
Cc: joe.perches@spirentcom.com, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: want opinions on possible glitch in 2.4 network error reporti ng
Date: Fri, 8 Feb 2002 08:35:29 +0000 [thread overview]
Message-ID: <20020208083529.65befc73.spyro@armlinux.org> (raw)
In-Reply-To: <Pine.LNX.3.95.1020207125644.8721A-100000@chaos.analogic.com>
In-Reply-To: <9384475DFC05D2118F9C00805F6F263107ECA811@exchange1.netcomsystems.com> <Pine.LNX.3.95.1020207125644.8721A-100000@chaos.analogic.com>
On a sunny Thu, 7 Feb 2002 13:08:24 -0500 (EST) Richard B. Johnson gathered
a sheaf of electrons and etched in their motions the following immortal
words:
> On Thu, 7 Feb 2002, Perches, Joe wrote:
> [SNIPPED..]
> > > That is correct UDP behaviour
> >
> > Do you think this is the correct PacketSocket/RAW behaviour?
>
> Yes.
>
> > How does one guarantee a send/sendto/write?
> > -
>
> Easy, you use send() or write(). These work on stream protocol TCP/IP
I know its an extreme case, but consider that something goes wrong and the
kernel ends up thinking its buffer is always full / zero lenngth /
something horrible.
I'd personally like it if it warned me it wasnt even trying to send my
packets, rather than just ignoring them completely...
next prev parent reply other threads:[~2002-02-08 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 17:37 want opinions on possible glitch in 2.4 network error reporti ng Perches, Joe
2002-02-07 18:08 ` Richard B. Johnson
2002-02-07 18:44 ` Chris Friesen
2002-02-07 19:51 ` Jan Harkes
2002-02-07 20:10 ` Chris Friesen
2002-02-07 20:33 ` Richard B. Johnson
2002-02-07 21:06 ` Chris Friesen
2002-02-07 21:29 ` Richard B. Johnson
2002-02-07 22:29 ` Mark Frazer
2002-02-08 8:35 ` Ian Molton [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-07 20:37 Perches, Joe
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=20020208083529.65befc73.spyro@armlinux.org \
--to=spyro@armlinux.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=joe.perches@spirentcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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