On 06/09/05, Kyle Brantley <[EMAIL PROTECTED]> wrote:
> Hi -
>
> I recently bought three rtl8169 gigabit cards, along with a gigabit
> switch. Trouble is, the computers keep freezing up once the NIC comes
> under and "decent" amount of load. Let me lay this out for you a bit:
>
> Computer A:
> -D
Hi -
I recently bought three rtl8169 gigabit cards, along with a gigabit
switch. Trouble is, the computers keep freezing up once the NIC comes
under and "decent" amount of load. Let me lay this out for you a bit:
Computer A:
-Dual AMD 2600+ MP
-rtl8169 under *64-bit PCI slot*
-2.6.12 (vanilla)
C
Benjamin LaHaise a écrit :
Please consider the patch below which makes use of file->private_data
to store the pointer to the socket, which avoids touching several
unused cachelines in the dentry and inode in sockfd_lookup.
Hi David
Could you please apply this patch, in continuation of Benj
BTW, _all_ callers of svc_getnl() have the form ntohl(svc_getnl(...)).
Which means that at least this one definitely should convert to host-endian
before returning...
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More major
applied patches 2-8
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
applied, please include a patch ordering in your Subject header next time.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
applied, please include a patch ordering in your Subject header next time.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
applied, please include a patch ordering in your Subject header next time.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
applied, please include a patch ordering in your Subject header next time.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
applied
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
applied 1-5
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
David S. Miller wrote:
You can, BTW, log the value of "__builtin_return_address(0)" at
the time of the neighbour table entry creation, so see who asked
for it. That might help track it down.
Yep, that was helpful. The caller is arp_bind_neighbour.
With regard to re-writing the ref-counting l
On Mon, Sep 05, 2005 at 10:55:58PM +0400, Alexey Dobriyan wrote:
> * usual s/u32/__be32/.
> * add svc_getnl(), svc_putnl() in spirit of svc_getu32(), svc_putu32().
> They return and accept __be32 instead of __u32, respectively.
> * convert to svc_getnl(), svc_putnl().
Umm... I'm not particulary
* usual s/u32/__be32/.
* add svc_getnl(), svc_putnl() in spirit of svc_getu32(), svc_putu32().
They return and accept __be32 instead of __u32, respectively.
* convert to svc_getnl(), svc_putnl().
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
---
include/linux/sunrpc/auth.h | 16
Pavel Machek wrote:
Hi!
I noticed that wireless patches are now in the mainline. That is good,
patches are getting smaller, but it is going to make future user
interface changes harder; and thats very bad.
There are good reasons to have wireless interfaces as wlanX, with
tcpdump showing wireles
Christoph Hellwig wrote:
On Mon, Sep 05, 2005 at 11:15:20AM +0300, Jouni Malinen wrote:
I understand removing the NULL pointers, but .name is actually a string
"NULL".. Leaving it to be NULL is not a very good idea. This "NULL"
algorithm was designed for cases where there is default algorithm f
On 9/5/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I wrote a few multicast tools, which use these multicast groups:
>
> 225.109.99.112
> ff02::6d63:7030
> 224.110.99.112
> ff02::6e63:7030
>
> I have a Cisco in the middle, and both boxes are in different VLANs.
> The Cisco
On Mon, 2005-09-05 at 15:37 +0200, Pavel Machek wrote:
> I noticed that wireless patches are now in the mainline. That is good,
> patches are getting smaller, but it is going to make future user
> interface changes harder; and thats very bad.
Only a very early version of the ieee80211 header was i
Hi!
> > There are good reasons to have wireless interfaces as wlanX, with
> > tcpdump showing wireless packetes, etc; but current patches name it
> > ethX, and you get plain ethernet packets on tcpdump. Are we going to
> > keep showing wireless interfaces as ethernet ones forever, or do we
> > pla
> Hi!
>
> I noticed that wireless patches are now in the mainline. That is good,
> patches are getting smaller, but it is going to make future user
> interface changes harder; and thats very bad.
Hi,
I'm also happy that these are in mainline now.
>
> There are good reasons to have wireless interf
Hi!
I noticed that wireless patches are now in the mainline. That is good,
patches are getting smaller, but it is going to make future user
interface changes harder; and thats very bad.
There are good reasons to have wireless interfaces as wlanX, with
tcpdump showing wireless packetes, etc; but c
Hi,
Pedro Ramalhais wrote:
> Yes, i might want to bring the card UP so that it can scan, but don't
> want to associate. Or bring the card UP and configure the card in
> Monitor mode. Or bring the card UP and configure the card in Master
> mode. Maybe ad-hoc too, not sure.
Yes, that sounds useful.
On Mon, Sep 05, 2005 at 11:15:20AM +0300, Jouni Malinen wrote:
> I understand removing the NULL pointers, but .name is actually a string
> "NULL".. Leaving it to be NULL is not a very good idea. This "NULL"
> algorithm was designed for cases where there is default algorithm for
> encryption and enc
All 5 patches applied, looks really good.
In particular, patch 4 with the prefetching, was particularly
nice to see :-)
Thanks a lot Michael.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kern
24 matches
Mail list logo
