Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+support\s+for\s+large\s+number\s+of\s+network\s+devices\.\s*$/: 34 ]

Total 34 documents matching your query.

1. [PATCH] support for large number of network devices. (score: 1)
Author: xxxxxx>
Date: Tue, 13 Jan 2004 15:46:10 -0800
When using pseudo network devices, and really big machines; there is sometimes a need to have a lot of network devices. This replaces the existing 2.6.1 limit of 100 entries an was O(n^2) with a algo
/archives/netdev/2004-01/msg00211.html (10,461 bytes)

2. Re: [PATCH] support for large number of network devices. (score: 1)
Author: xxxxxx>
Date: Tue, 13 Jan 2004 15:59:21 -0800
I think your code has different semantics than exist currently. For example, let's use the example of asking for "slip%d" then "eth%d". The existing code would hand out "slip0" then "eth0", but your
/archives/netdev/2004-01/msg00213.html (9,585 bytes)

3. Re: [PATCH] support for large number of network devices. (score: 1)
Author: xxxxxx>
Date: Tue, 13 Jan 2004 16:13:03 -0800
It uses the output format string for the sscanf match, and since sscanf formats have to match. sscanf("eth0", "slip%d", &i) returns 0 so eth0 would be skipped
/archives/netdev/2004-01/msg00215.html (10,507 bytes)

4. Re: [PATCH] support for large number of network devices. (score: 1)
Author: xxxxxx>
Date: Tue, 13 Jan 2004 16:23:25 -0800
Stephen Hemminger wrote: When using pseudo network devices, and really big machines; there is sometimes a need to have a lot of network devices. This replaces the existing 2.6.1 limit of 100 entries
/archives/netdev/2004-01/msg00217.html (10,561 bytes)

5. Re: [PATCH] support for large number of network devices. (score: 1)
Author: xxxxxx>
Date: Tue, 13 Jan 2004 16:38:28 -0800
I have a patch for name hashing, but don't know if it's needed. Even without it I can add 9 thousand bridge entries, and each one takes longer to start the command than add the entry now.
/archives/netdev/2004-01/msg00223.html (10,491 bytes)

6. Re: [PATCH] support for large number of network devices. (score: 1)
Author: xxxxxx>
Date: Tue, 13 Jan 2004 17:55:32 -0800
Stephen Hemminger wrote: On Tue, 13 Jan 2004 16:23:25 -0800 Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: Stephen Hemminger wrote: When using pseudo network devices, and really big machines; there is s
/archives/netdev/2004-01/msg00225.html (11,656 bytes)

7. Re: [PATCH] support for large number of network devices. (score: 1)
Author: xxxxxx>
Date: Wed, 14 Jan 2004 01:13:03 -0600
Unfortunately sscanf("eth0-not-allocated", "eth%d", &i) fools it. Which may or may not be worth worrying about. -- Matt Mackall : http://www.selenic.com : Linux development and consulting
/archives/netdev/2004-01/msg00226.html (11,350 bytes)

8. Re: [PATCH] support for large number of network devices. (score: 1)
Author: xxxxxx>
Date: Tue, 13 Jan 2004 23:18:25 -0800
I found some other fast-path'ish cases of dev_get_by_name(), one of which is atalk_rcv()'s handling of IP over DDP packets. I didn't even search around for __dev_get() and dev_get_by_index() cases. T
/archives/netdev/2004-01/msg00227.html (10,639 bytes)

9. Re: [PATCH] support for large number of network devices. (score: 1)
Author: xxxxxx>
Date: Tue, 13 Jan 2004 23:54:56 -0800
David S. Miller wrote: Therefore, I think it's wise to just do this right from the start and use a hash. Stephen can you test up and submit the netdev name hash patch you have? In case it proves usef
/archives/netdev/2004-01/msg00233.html (10,988 bytes)

10. Re: [PATCH] support for large number of network devices. (score: 1)
Author: val@xxxxxxxxxx>
Date: Wed, 14 Jan 2004 11:37:34 -0800
Hmmm, the old code would have assigned "eth0" in that case, new code would assign "eth1". Other difference is in the case of whitespace. scanf("white space0", "white space%d", &i) because any whites
/archives/netdev/2004-01/msg00244.html (10,268 bytes)

11. Re: [PATCH] support for large number of network devices. (score: 1)
Author: inger@xxxxxxxx>
Date: Wed, 14 Jan 2004 13:51:57 -0600
I think it's probably easier to just add O(1) lookup and then do explicit lookups on eth0..ethx. As Dave's pointed out, fast lookups are wanted elsewhere. I made a quick hack to make the sscanf trick
/archives/netdev/2004-01/msg00245.html (11,089 bytes)

12. Re: [PATCH] support for large number of network devices. (score: 1)
Author: pm@xxxxxxxxxxx>
Date: Wed, 14 Jan 2004 12:11:55 -0800
My only concern right now is that, since we're in the middle of 2.6.x, we not break semantics of such a core routine like this one. Although I'm willing to accept that certain cases are just rediculi
/archives/netdev/2004-01/msg00246.html (11,079 bytes)

13. Re: [PATCH] support for large number of network devices. (score: 1)
Author: vem@xxxxxxxxxx>
Date: Wed, 14 Jan 2004 13:39:08 -0800
You may want to be careful about buffer overflow in '%d' with a most 2 char ('0' to '99'). The new code may create overflow for device names such as : 'reallylongname%d' And you don't seem the catch
/archives/netdev/2004-01/msg00247.html (10,111 bytes)

14. Re: [PATCH] support for large number of network devices. (score: 1)
Author: rle@xxxxxxxxxx>
Date: Wed, 14 Jan 2004 16:24:11 -0800
This should make it match the existing semantics more exactly. It will skip the false positive matchs from sscanf trailing chars or blanks. diff -Nru a/net/core/dev.c b/net/core/dev.c -- a/net/core/d
/archives/netdev/2004-01/msg00259.html (11,735 bytes)

15. Re: [PATCH] support for large number of network devices. (score: 1)
Author: vem@xxxxxxxxxx>
Date: Thu, 15 Jan 2004 00:46:31 -0800
Ok, but... I thought we had decided to move towards the hashing based patch you said you had so we can kill two birds with one stone? At least, that is the conclusion I thought we had arrived at.
/archives/netdev/2004-01/msg00273.html (10,755 bytes)

16. Re: [PATCH] support for large number of network devices. (score: 1)
Author: 藤英明 <yoshfuji@xxxxxxxxxxxxxx>
Date: Thu, 15 Jan 2004 09:52:52 -0800
The right way is a combination of the two pass dev_alloc_name and hashing the names. Both work together
/archives/netdev/2004-01/msg00300.html (11,451 bytes)

17. Re: [PATCH] support for large number of network devices. (score: 1)
Author: ideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
Date: Thu, 15 Jan 2004 11:40:25 -0800
Ok, please resend the final version of your dev_alloc_name() bitmap patch under seperate cover so I can apply it, thanks.
/archives/netdev/2004-01/msg00315.html (11,367 bytes)

18. [PATCH] support for large number of network devices. (score: 1)
Author: Stephen Hemminger <shemminger@xxxxxxxx>
Date: Tue, 13 Jan 2004 15:46:10 -0800
When using pseudo network devices, and really big machines; there is sometimes a need to have a lot of network devices. This replaces the existing 2.6.1 limit of 100 entries an was O(n^2) with a algo
/archives/netdev/2004-01/msg00919.html (10,461 bytes)

19. Re: [PATCH] support for large number of network devices. (score: 1)
Author: "David S. Miller" <davem@xxxxxxxxxx>
Date: Tue, 13 Jan 2004 15:59:21 -0800
I think your code has different semantics than exist currently. For example, let's use the example of asking for "slip%d" then "eth%d". The existing code would hand out "slip0" then "eth0", but your
/archives/netdev/2004-01/msg00921.html (9,669 bytes)

20. Re: [PATCH] support for large number of network devices. (score: 1)
Author: Stephen Hemminger <shemminger@xxxxxxxx>
Date: Tue, 13 Jan 2004 16:13:03 -0800
It uses the output format string for the sscanf match, and since sscanf formats have to match. sscanf("eth0", "slip%d", &i) returns 0 so eth0 would be skipped
/archives/netdev/2004-01/msg00923.html (10,623 bytes)


This search system is powered by Namazu