netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: jamal <hadi@cyberus.ca>
Cc: Eric Lemoine <Eric.Lemoine@ens-lyon.fr>, netdev@oss.sgi.com
Subject: Re: udp weirdness
Date: Fri, 27 Sep 2002 18:04:12 +0300	[thread overview]
Message-ID: <20020927150412.GI30392@mea-ext.zmailer.org> (raw)
In-Reply-To: <Pine.GSO.4.30.0209271048160.4401-100000@shell.cyberus.ca>

On Fri, Sep 27, 2002 at 10:53:00AM -0400, jamal wrote:
> On Fri, 27 Sep 2002, Eric Lemoine wrote:
> 
> > I figured out that packets can be dropped in pfifo_fast_enqueue()
> > [the default qdisc's enqueue func], even though the driver/kernel
> > flow control has triggered.
...
> What trigger do you suggest to wake up the process again?
> A better idea maybe to return something to the socket so it can
> manage things instead -- not sure what to return though that wouldnt
> break some standard;


"man sendto" error return codes:

       ENOBUFS
              The  output queue for a network interface was full.
              This generally indicates  that  the  interface  has
              stopped  sending,  but  may  be caused by transient
              congestion.  (This cannot occur in  Linux,  packets
              are just silently dropped when a device queue over­
              flows.)

> cheers,
> jamal

/Matti Aarnio

  reply	other threads:[~2002-09-27 15:04 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-24  6:50 udp weirdness Eric Lemoine
2002-09-27 12:02 ` Eric Lemoine
2002-09-27 14:53   ` jamal
2002-09-27 15:04     ` Matti Aarnio [this message]
2002-09-29 14:47       ` jamal
2002-09-30  8:49         ` Eric Lemoine
2002-09-30 11:09           ` jamal
2002-09-30 12:10           ` jamal
2002-09-30 12:23             ` jamal
2002-10-01  0:22               ` PATCH " jamal
2002-10-01  6:35                 ` Eric Lemoine
2002-10-01  9:51                   ` jamal
2002-10-01 13:53                 ` kuznet
2002-10-01 14:14                   ` jamal
2002-10-01 14:26                   ` Chris Friesen
2002-10-01 14:40                     ` kuznet
2002-10-01 14:52                       ` Chris Friesen
2002-10-01 15:31                         ` kuznet
2002-10-01 16:16                           ` Chris Friesen
2002-10-01 16:41                             ` kuznet
2002-10-01 17:17                               ` Chris Friesen
2002-10-01 16:42                           ` Ben Greear
2002-10-01 16:58                             ` Chris Friesen
2002-10-01 17:55                             ` jamal
2002-10-01 18:36                               ` Chris Friesen
2002-10-01 18:35                                 ` jamal
2002-10-01 18:54                                   ` Ben Greear
2002-10-01 19:03                                   ` Chris Friesen
2002-10-01 18:52                               ` Ben Greear
2002-10-02 11:13                           ` Eric Lemoine
2002-10-02 14:09                             ` Chris Friesen
2002-10-02 15:25                             ` Ben Greear
2002-10-03 15:58                               ` Eric Lemoine
2002-10-03 16:29                                 ` kuznet
2002-09-27 15:19     ` Eric Lemoine
2002-09-27 15:57     ` Eric Lemoine

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=20020927150412.GI30392@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=Eric.Lemoine@ens-lyon.fr \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).