From: Tommy Christensen <tommy.christensen@tpack.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>,
"Linux 802.1Q VLAN" <vlan@candelatech.com>,
Francois Romieu <romieu@fr.zoreil.com>,
"David S. Miller" <davem@redhat.com>
Subject: Re: [PATCH] 802.1Q VLAN
Date: Sat, 30 Oct 2004 02:31:02 +0200 [thread overview]
Message-ID: <4182E0C6.6090205@tpack.net> (raw)
In-Reply-To: <4182DABE.7000502@candelatech.com>
Ben Greear wrote:
> Can't you also add a queue to a VLAN device?
Sure you can. This is the best solution, if you have a way of
waking up the queue.
>> Nice. This idea is definitely worth persuing. However, ideally we
>> would want to be notified when the *qdisc* queue opens up - this
>> is our "tx ring buffer".
>
>
> Maybe the qdisc could automatically flush what it could to lower
> level devices/queues whenever it was asked to enqueue a packet?
> This way, waking the writers could automatically wake the various
> queues under the writers.
>
> That could be happening already, and might explain why my pktgen hacks
> work.
Yes, this is what qdisc does. It just isn't good enough to have to
wait for the next packet, IMO.
-Tommy
next prev parent reply other threads:[~2004-10-30 0:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 21:07 [PATCH] 802.1Q VLAN Ben Greear
2004-10-22 21:46 ` Francois Romieu
2004-10-22 22:09 ` Ben Greear
2004-10-23 0:24 ` Francois Romieu
2004-10-25 20:51 ` Ben Greear
2004-10-25 23:56 ` Ben Greear
2004-10-27 1:02 ` David S. Miller
2004-10-27 23:49 ` David S. Miller
2004-10-28 1:28 ` Ben Greear
2004-10-28 4:42 ` David S. Miller
2004-10-28 23:40 ` Tommy Christensen
2004-10-28 23:35 ` David S. Miller
2004-10-29 0:23 ` Ben Greear
2004-10-29 0:38 ` Krzysztof Halasa
2004-10-29 8:29 ` Tommy Christensen
2004-10-29 17:45 ` Ben Greear
2004-10-29 23:37 ` Tommy Christensen
2004-10-29 23:56 ` Ben Greear
2004-10-30 0:05 ` Ben Greear
2004-10-30 0:31 ` Tommy Christensen [this message]
2004-11-01 18:58 ` Ben Greear
2004-11-01 23:08 ` Tommy Christensen
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=4182E0C6.6090205@tpack.net \
--to=tommy.christensen@tpack.net \
--cc=davem@redhat.com \
--cc=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.com \
--cc=vlan@candelatech.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 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.