Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*RFC\:\s+Reporting\s+dropped\s+packets\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*RFC\:\s+Reporting\s+dropped\s+packets\s*$/: 6 ]

Total 6 documents matching your query.

1. RFC: Reporting dropped packets (score: 1): Author: xxxx>; Date: Wed, 21 Jun 2000 17:59:59 +1000; There are a number of places in the network code where we drop packets which people might be interested in knowing about (eg. my nat code, CONFIG_IP_ROUTE_VERBOSE). Be very nice if these were more fl; /archives/netdev/2000-06/msg00241.html (7,339 bytes)
2. Re: RFC: Reporting dropped packets (score: 1): Author: xxxx>; Date: Thu, 22 Jun 2000 03:37:48 +0000; Does this affect drivers? Incoming packes dropped due to OOM, outgoing due to error recovery.; /archives/netdev/2000-06/msg00244.html (7,258 bytes)
3. Re: RFC: Reporting dropped packets (score: 1): Author: xxxx>; Date: Thu, 22 Jun 2000 16:42:39 +1000; No, only systematic (`interesting') *IP* packet drops, not random ones. Trying to cover all packet drops was my original mistake, and is fairly useless (turns out that `drop' is a vague definition: d; /archives/netdev/2000-06/msg00245.html (7,549 bytes)
4. RFC: Reporting dropped packets (score: 1): Author: Rusty Russell <rusty@xxxxxxxxxxxxxxxx>; Date: Wed, 21 Jun 2000 17:59:59 +1000; There are a number of places in the network code where we drop packets which people might be interested in knowing about (eg. my nat code, CONFIG_IP_ROUTE_VERBOSE). Be very nice if these were more fl; /archives/netdev/2000-06/msg00540.html (7,339 bytes)
5. Re: RFC: Reporting dropped packets (score: 1): Author: Andrew Morton <andrewm@xxxxxxxxxx>; Date: Thu, 22 Jun 2000 03:37:48 +0000; Does this affect drivers? Incoming packes dropped due to OOM, outgoing due to error recovery.; /archives/netdev/2000-06/msg00543.html (7,318 bytes)
6. Re: RFC: Reporting dropped packets (score: 1): Author: Rusty Russell <rusty@xxxxxxxxxxxxxxxx>; Date: Thu, 22 Jun 2000 16:42:39 +1000; No, only systematic (`interesting') *IP* packet drops, not random ones. Trying to cover all packet drops was my original mistake, and is fairly useless (turns out that `drop' is a vague definition: d; /archives/netdev/2000-06/msg00544.html (7,573 bytes)

Current List: 1 - 6
Page: [1]