[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071009183027.GA552@one.firstfloor.org>
Date: Tue, 9 Oct 2007 20:30:27 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Stephen Hemminger <shemminger@...ux-foundation.org>
Cc: Andi Kleen <andi@...stfloor.org>,
David Miller <davem@...emloft.net>, jeff@...zik.org,
johnpol@....mipt.ru, herbert@...dor.apana.org.au,
gaagaan@...il.com, Robert.Olsson@...a.slu.se,
netdev@...r.kernel.org, rdreier@...co.com,
peter.p.waskiewicz.jr@...el.com, hadi@...erus.ca,
mcarlson@...adcom.com, jagana@...ibm.com,
general@...ts.openfabrics.org, mchan@...adcom.com, tgraf@...g.ch,
randy.dunlap@...cle.com, sri@...ibm.com, kaber@...sh.net
Subject: Re: [ofa-general] Re: [PATCH 2/3][NET_BATCH] net core use batching
> I wonder about the whole idea of queueing in general at such high speeds.
> Given the normal bi-modal distribution of packets, and the predominance
> of 1500 byte MTU; does it make sense to even have any queueing in software
> at all?
Yes that is my point -- it should just pass it through directly
and the driver can then put it into the different per CPU (or per
whatever) queues managed by the hardware.
The only thing the qdisc needs to do is to set some bit that says
"it is ok to put this into difference queues; don't need strict ordering"
Otherwise if the drivers did that unconditionally they might cause
problems with other qdiscs.
This would also require that the driver exports some hint
to the upper layer on how large its internal queues are. A device
with a short queue would still require pfifo_fast. Long queue
devices could just pass through. That again could be a single flag.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists