Re: [PATCH] ixgb: add PCI Error recovery callbacks

2006-07-02 Thread Zhang, Yanmin
On Fri, 2006-06-30 at 00:26, Linas Vepstas wrote: > Adds PCI Error recovery callbacks to the Intel 10-gigabit ethernet > ixgb device driver. Lightly tested, works. > > Signed-off-by: Linas Vepstas <[EMAIL PROTECTED]> > +/** > + * ixgb_io_error_detected() - called when PCI error is detected > + * @

[PATCH] ipvs: Add sysctl documentation

2006-07-02 Thread Horms
* Derived from http://www.linuxvirtualserver.org/docs/sysctl.html, v1.4 maintained by Wensong Zhang * Adjusted preample to match ip-sysctl.txt * Sorted options into alphabetical order * Added expire_quiescent_template * Removed timeout_* which are no longer present * Incoporated doc/debug-le

Re: [Patch][RFC] Disabling per-tgid stats on task exit in taskstats

2006-07-02 Thread Paul Jackson
Shailabh wrote: > Sends a separate "registration" message with cpumask to listen to. > Kernel stores (real) pid and cpumask. Question: = Ah - good. So this means that I could configure a system with a fork/exit intensive, performance critical job on some dedicated CPUs, and be able to c

Re: netif_stop_queue() and multiple hardware queues

2006-07-02 Thread David Miller
From: Jeremy Jackson <[EMAIL PROTECTED]> Date: Sun, 02 Jul 2006 22:36:03 -0400 > I propose that this is an architecture/framework/API issue that the > Linux core networking code should be dealing with. Proposals are worthless if nobody wants to do the work to actually implement the proposal. Yo

Re: netif_stop_queue() and multiple hardware queues

2006-07-02 Thread Jeremy Jackson
I'd like to raise the question again. How can the network stack's flow control function with hardware that has multiple physical queues? How can these queues be exposed to tc? After scanning the netdev mailing list activity for the last 6 months, I can see no furthur discussion since my orig

Re: IPVS Sysctl Variables

2006-07-02 Thread Horms
On Fri, Jun 30, 2006 at 02:20:45PM -0700, David Miller wrote: > From: Horms <[EMAIL PROTECTED]> > Date: Fri, 30 Jun 2006 15:19:41 +0900 > > > there are quite a number of entries under /proc/sys/net/ipv4/vs, > > I swear that they were documented in Documentation/networking/ > > at some stage, but p

[PATCH 2/2] ATM: add+use poison defines

2006-07-02 Thread Randy.Dunlap
From: Randy Dunlap <[EMAIL PROTECTED]> ATM: add and use POISON define values. Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]> --- drivers/atm/ambassador.c |3 ++- drivers/atm/idt77252.c |3 ++- include/linux/poison.h |1 + 3 files changed, 5 insertions(+), 2 deletions(-) --- lin

[PATCH] net: add+use poison defines

2006-07-02 Thread Randy.Dunlap
From: Randy Dunlap <[EMAIL PROTECTED]> Add and use poison defines in net/. Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]> --- include/linux/poison.h |4 net/atm/clip.c |3 ++- net/ipv6/netfilter/ip6_tables.c |3 ++- 3 files changed, 8 insertions(+), 2

[PATCH] xfrm6: move define/ifdef check order

2006-07-02 Thread Randy.Dunlap
From: Randy Dunlap <[EMAIL PROTECTED]> The first check for #ifdef XFRM6_TUNNEL_SPI_MAGIC needs to come after the optional #define of it, otherwise the variable won't be there for the rest of the code to use. Shouldn't that CONFIG_IPV6_XFRM6_TUNNEL_DEBUG be part of Kconfig or have its name changed

Merci pour la réponce ( votre frère Mr.P.Kamara )

2006-07-02 Thread PETER KAMARA
Mr Peter KAMARA Email: [EMAIL PROTECTED] Tel : 00229 97 17 75 85. Mon cher, Je sais que mon message sera d'une grande surprise quand il vous parviendra. Donc' je vous présente toutes mes excuses. J’ai prie pendant plusieurs jours et après cela j'ai choisi de vous contacter parmi plusieurs au

[RESEND] please pull from git://lost.foo-projects.org/~ahkok/git/netdev-2.6 upstream

2006-07-02 Thread Auke Kok
Jeff, Since my pull request from thursday I haven't heard anything anymore, so I assume that the changes we made were sufficient. Needless to say that I would love to see ich8 support make it into 2.6.18rc, considering that the hardware already is out there and the code has been tested and valid

[IPROUTE2] Generic netlink interface

2006-07-02 Thread jamal
very quiet today .. Stephen, I've been sitting on this for a while now; just tested against latest kernels. Another one on top of the other i.e against iproute2-git. Shailabh, if you have time can you try just listing things, monitoring etc; I dont think your tool fits here - but if you could

Re: Belkin F5D7001de locks up my Athlon64 system

2006-07-02 Thread Michael Buesch
On Sunday 02 July 2006 13:32, Johann Uhrmann wrote: > here is another log from the 2.6.17-mm4 kernel. This oops was the only > one since reboot: > > bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: > drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1490:bc)[ 87.484118] bcm43xx: > ASSERTION FAI

Re: 2.6.17: networking bug??

2006-07-02 Thread Jan Knutar
On Tuesday 13 June 2006 20:39, John Heffner wrote: > The best thing you can do is try to find this broken box and inform its > owner that it needs to be fixed. (If you can find out what it is, I'd > be interested to know.) In the meantime, disabling window scaling will > work around the probl

[IPROUTE]: Introduce tc monitor

2006-07-02 Thread jamal
Speaking of events reminded me of this.. Managed to get some quality time, so heres a patch against current iproute2 git that adds something useful. Stephen, please apply. cheers, jamal This patch adds ability to monitor tc events similar to ipmonitor. User runs "tc monitor" (without quotes) an

Re: Two I/O memory regions in /proc/iomem for a NIC

2006-07-02 Thread John Que
Hello, Thanks for your answers. I checked again: On the machine with e1000 driver, it was in fact a machine with 2 e1000 NICs. However, if I am not wrong, it happened I also saw 2 I/O regions on a machine with one NIC (RealTek 8139too) when typing cat /proc/iomem. I am not sure though. Let me

Re: [PATCH 0/2] NET: Accurate packet scheduling for ATM/ADSL

2006-07-02 Thread jamal
On Sun, 2006-02-07 at 06:23 +0200, Patrick McHardy wrote: [..] > > - Any message to user space may be lost whether it has ifi_change or > > not. You need some way to figure out a message was lost and declare your > > state may be invalid. The -ENOBUFs is one way to discover stale state. > > Thats

Re: Two I/O memory regions in /proc/iomem for a NIC

2006-07-02 Thread Jeff Garzik
On Sun, Jul 02, 2006 at 10:24:10AM +0300, John Que wrote: > Hello, > > I had noticed that there are machines where > if I ran cat /proc/iomem I see one I/O memory region for the NIC > I am using; while there are other machines where > I see 2 regions for the NIC I/O memory. > > For example, on a

Re: Two I/O memory regions in /proc/iomem for a NIC

2006-07-02 Thread Lennert Buytenhek
On Sun, Jul 02, 2006 at 10:24:10AM +0300, John Que wrote: > I had noticed that there are machines where > if I ran cat /proc/iomem I see one I/O memory region for the NIC > I am using; while there are other machines where > I see 2 regions for the NIC I/O memory. > > For example, on a machine wit

Two I/O memory regions in /proc/iomem for a NIC

2006-07-02 Thread John Que
Hello, I had noticed that there are machines where if I ran cat /proc/iomem I see one I/O memory region for the NIC I am using; while there are other machines where I see 2 regions for the NIC I/O memory. For example, on a machine with e1000 NIC adapter, I see the following 2 I/O memory regions