Re: [PATCH 3/3] pkt_sched: restore multiqueue prio scheduler | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
From: Jarek Poplawski <jarkao2@xxxxxxxxx> Date: Mon, 25 Aug 2008 07:57:44 +0000 > On Mon, Aug 25, 2008 at 12:48:25AM -0700, David Miller wrote: > > From: Jarek Poplawski <jarkao2@xxxxxxxxx> > > Date: Mon, 25 Aug 2008 06:06:40 +0000 > > > > If we feed packets after the first one to the card, we would not > > be implementing a FIFO. > > Not necessarilly so: if separate flows are hashed to "their" hwqueues, > a FIFO per flow would be still obeyed. What appears on the wire is still going to be similar. You have to subsequently ask if it's worth the complexity to do what you seem to be proposing. When a single hardware queue fills up, it's the SAME, semantically, as when a unary TX queue of a traditional device fills up. There is NO on the wire difference. There will be NO performance difference, because the device will have work to do as by definition of one TX queue being full there are some packets queued up to the device. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Kernel List] [Site Home] [Ethernet Bridging] [Git] [IETF Annouce] [Linux Assembly] [VLAN] [Networking] [Security] [Bugtraq] [Rubini] [Photo] [Singles Social Netowrking] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Virtualization] [Linux Security] [Linux IDE] [Linux RAID] [Linux SCSI] [Linux Wireless] [DDR & Rambus] [Free Dating] [Linux Resources] [Wireless Reading Device]
![]() |
![]() |