hi,
i've always found it unfortunate that sfq includes the destination port in
the hash because so-called "download accelerators" which issue a bunch of
simultaneous http range-requests with non-overlapping ranges end up
getting an unfair share of the bandwidth. so i've modified sfq with an
o
From: Krzysztof Oledzki <[EMAIL PROTECTED]>
Date: Fri, 16 Dec 2005 13:15:58 +0100 (CET)
> Thank you! Will test ASAP. Need day or two, I need to reassemble my
> IPSec netlab. ;)
Please let me know if it works as soon as you know.
I think for now it's more important to have things working than to
> okay, thanks for the report, adding netdev
> On 10/29/05, Folkert van Heusden <[EMAIL PROTECTED]> wrote:
> > Reproducable i get a kernel panic when inserting the e1000 module on my
> > system. Kernel 2.6.13.3.
> > It is P4 with hyperthreading enabled. 1GB ram.
> > lspci output:
> > 00:00.0 Host b
John W. Linville wrote:
I am now... :-) But, I still don't seem to see any problem. Are there
specific tests I should run?
There are multiple nforce versions - which one do you use?
For example only the most recent one supports 64-bit dma, perhaps
something with the 64-bit code is broken
On Fri, Dec 16, 2005 at 11:15:17PM -0800, David S. Miller wrote:
> From: Andi Kleen <[EMAIL PROTECTED]>
> Date: Sat, 17 Dec 2005 08:10:29 +0100
>
> > sock_init can be done as a core_initcall instead of calling
> > it directly in init/main.c
> >
> > Also I removed an out of date #ifdef.
> >
> > S
On Fri, Dec 16, 2005 at 02:34:28PM -0800, David S. Miller wrote:
> From: Benjamin LaHaise <[EMAIL PROTECTED]>
> Date: Fri, 16 Dec 2005 15:58:57 -0500
>
> > On Fri, Dec 16, 2005 at 12:59:57PM -0800, Joe Perches wrote:
> > > How about moving this into a helper function
> > > and calling it from allo
[Sorry for posting on this list, but I didn't have any response on
linux-net]
Hello.
I have a pretty strange problem with routing and iptables mark.
My firewall has a classic 3 NIC config: one nic connected to the
ISP routers, one network for DMZ and the third network for my
private network. Her
I noticed that some of 'struct proto_ops' used in the kernel may share a cache
line used by locks or other heavily modified data. (default linker alignement
is 32 bytes, and L1_CACHE_LINE is 64 or 128 at least)
This patch makes sure a 'struct proto_ops' can be declared as const, so that
all cp
