Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TG3\]\:\s+About\s+hw\s+coalescing\s+infrastructure\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TG3\]\:\s+About\s+hw\s+coalescing\s+infrastructure\.\s*$/: 28 ]

Total 28 documents matching your query.

1. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: Eric Dumazet <dada1@xxxxxxxxxxxxx>; Date: Mon, 04 Jul 2005 23:22:12 +0200; Michael Chan a écrit : On Wed, 2005-06-22 at 17:25 +0200, Eric Dumazet wrote: Is there anything I can try to tune the coalescing ? Being able to handle 100 packets each interrupt instead of one or; /archives/netdev/2005-07/msg00032.html (13,903 bytes)
2. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxxxxx>; Date: Mon, 04 Jul 2005 14:26:04 -0700 (PDT); Does this happen without changing the coalescing settings at all?; /archives/netdev/2005-07/msg00033.html (9,333 bytes)
3. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: Eric Dumazet <dada1@xxxxxxxxxxxxx>; Date: Mon, 04 Jul 2005 23:39:35 +0200; David S. Miller a écrit : From: Eric Dumazet <dada1@xxxxxxxxxxxxx> Date: Mon, 04 Jul 2005 23:22:12 +0200 But it seems something is wrong because when network load becomes high I get : Jul 4 23:01:1; /archives/netdev/2005-07/msg00034.html (10,218 bytes)
4. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxxxxx>; Date: Mon, 04 Jul 2005 14:49:51 -0700 (PDT); Thanks.; /archives/netdev/2005-07/msg00035.html (9,221 bytes)
5. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: Eric Dumazet <dada1@xxxxxxxxxxxxx>; Date: Tue, 05 Jul 2005 00:31:55 +0200; Eric Dumazet a écrit : David S. Miller a écrit : From: Eric Dumazet <dada1@xxxxxxxxxxxxx> Date: Mon, 04 Jul 2005 23:22:12 +0200 But it seems something is wrong because when network load becomes high; /archives/netdev/2005-07/msg00036.html (11,160 bytes)
6. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: Eric Dumazet <dada1@xxxxxxxxxxxxx>; Date: Tue, 05 Jul 2005 00:47:56 +0200; Eric Dumazet a écrit : Oops, I forgot to tell you I applied the patch : [TG3]: Eliminate all hw IRQ handler spinlocks. (Date: Fri, 03 Jun 2005 12:25:58 -0700 (PDT)) Maybe I should revert to stock 2; /archives/netdev/2005-07/msg00037.html (9,966 bytes)
7. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxxxxx>; Date: Mon, 04 Jul 2005 15:47:12 -0700 (PDT); Please don't ever do stuff like that :-( That makes the driver version, and any other information you report completely meaningless and useless. You've just wasted a lot of our time. I have no idea t; /archives/netdev/2005-07/msg00038.html (10,075 bytes)
8. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: Eric Dumazet <dada1@xxxxxxxxxxxxx>; Date: Tue, 05 Jul 2005 00:55:37 +0200; David S. Miller a écrit : Please don't ever do stuff like that :-( That makes the driver version, and any other information you report completely meaningless and useless. You've just wasted a lot o; /archives/netdev/2005-07/msg00039.html (10,922 bytes)
9. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: Eric Dumazet <dada1@xxxxxxxxxxxxx>; Date: Tue, 05 Jul 2005 00:57:58 +0200; Eric Dumazet a écrit : For your information, 2.6.13-rc1 locks too. Very easy way to lock it : ping -f some_destination. Arg. False alarm. Sorry. Time for me to sleep; /archives/netdev/2005-07/msg00040.html (10,557 bytes)
10. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxxxxx>; Date: Mon, 04 Jul 2005 16:00:34 -0700 (PDT); The case here is that you didn't even mention that you had the patch applied. If you don't say what changes you've applied to the stock driver we can't properly debug anything. SMP system? What platf; /archives/netdev/2005-07/msg00041.html (9,905 bytes)
11. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxxxxx>; Date: Mon, 04 Jul 2005 16:01:40 -0700 (PDT); Oh well...; /archives/netdev/2005-07/msg00042.html (10,056 bytes)
12. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: Eric Dumazet <dada1@xxxxxxxxxxxxx>; Date: Tue, 05 Jul 2005 18:14:59 +0200; David S. Miller a écrit : SMP system? What platform and 570x chip revision? dual opterons 248, Ethernet controller: Broadcom Corporation NetXtreme BCM5702 Gigabit Ethernet (rev 02) Does the stock d; /archives/netdev/2005-07/msg00050.html (10,467 bytes)
13. [TG3]: About hw coalescing infrastructure. (score: 1): Author: yer@xxxxxxxxxx>; Date: Wed, 22 Jun 2005 17:25:08 +0200; route]# ./a.out; /archives/netdev/2005-06/msg00525.html (16,526 bytes)
14. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: n" <leonid.grossman@xxxxxxxxxxxx>; Date: Wed, 22 Jun 2005 12:03:32 -0700; ? cheers, jamal; /archives/netdev/2005-06/msg00534.html (8,265 bytes)
15. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: Eric Dumazet <dada1@xxxxxxxxxxxxx>; Date: Mon, 04 Jul 2005 23:22:12 +0200; Is there anything I can try to tune the coalescing ? Being able to handle 100 packets each interrupt instead of one or two would certainly help. I dont mind about latency. But of course I would like; /archives/netdev/2005-07/msg00256.html (13,537 bytes)
16. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxxxxx>; Date: Mon, 04 Jul 2005 14:26:04 -0700 (PDT); Does this happen without changing the coalescing settings at all?; /archives/netdev/2005-07/msg00257.html (9,493 bytes)
17. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: Eric Dumazet <dada1@xxxxxxxxxxxxx>; Date: Mon, 04 Jul 2005 23:39:35 +0200; But it seems something is wrong because when network load becomes high I get : Jul 4 23:01:19 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out Jul 4 23:01:19 dada1 kernel: tg3: eth0: transmit; /archives/netdev/2005-07/msg00258.html (10,363 bytes)
18. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxxxxx>; Date: Mon, 04 Jul 2005 14:49:51 -0700 (PDT); Thanks.; /archives/netdev/2005-07/msg00259.html (9,331 bytes)
19. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: Eric Dumazet <dada1@xxxxxxxxxxxxx>; Date: Tue, 05 Jul 2005 00:31:55 +0200; Eric Dumazet a écrit : David S. Miller a écrit : But it seems something is wrong because when network load becomes high I get : Jul 4 23:01:19 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out; /archives/netdev/2005-07/msg00260.html (11,272 bytes)
20. Re: [TG3]: About hw coalescing infrastructure. (score: 1): Author: Eric Dumazet <dada1@xxxxxxxxxxxxx>; Date: Tue, 05 Jul 2005 00:47:56 +0200; Eric Dumazet a écrit : Oops, I forgot to tell you I applied the patch : [TG3]: Eliminate all hw IRQ handler spinlocks. (Date: Fri, 03 Jun 2005 12:25:58 -0700 (PDT)) Maybe I should revert to stock 2.6; /archives/netdev/2005-07/msg00261.html (10,106 bytes)

Current List: 1 - 20
Page: [1] [2]