From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Are multiple output queues in qdisc possible?
Date: Fri, 07 May 2004 18:44:39 +0000 [thread overview]
Message-ID: <409BD917.6020809@dsl.pipex.com> (raw)
In-Reply-To: <52E3FE33.0FB6EAD8.0B6A2FAE@aol.com>
EyeManBill@aol.com wrote:
> Our system sets up multiple connections. At times, packets can be transmitted for some connections but not others.
>
> With that in mind:
>
> 1. Is it possible to have multiple output queues in a qdisc,
> rather than one?
>
> 2. Can a packet that leaves qdisc be returned to qdisc if it
> cannot be transmitted?
>
> If so, how?
Don't really know about 1.
2. - there is a requeue function in the queues in net/sched and a
comment in sch_api.c -
---requeue
requeues once dequeued packet. It is used for non-standard or
just buggy devices, which can defer output even if dev->tbusy=0.
I guess that gives a bit of hope.
Andy.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-05-07 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 0:33 [LARTC] Are multiple output queues in qdisc possible? EyeManBill
2004-05-07 18:44 ` Andy Furniss [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=409BD917.6020809@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=lartc@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.