On Thu, Jan 18, 2007 at 10:10:47PM -0500, Jeff Garzik wrote:
John W. Linville wrote:
The following changes since commit
10764889c6355cbb335cf0578ce12427475d1a65:
Larry Finger (1):
bcm43xx: Fix failure to deliver PCI-E interrupts
are found in the git repository at:
On Friday 19 January 2007 10:27, Eric W. Biederman wrote:
YOSHIFUJI Hideaki / 吉藤英明 [EMAIL PROTECTED] writes:
In article [EMAIL PROTECTED] (at Wed, 17 Jan 2007 18:51:14
+0300), Dmitry Mishin [EMAIL PROTECTED] says:
===
L2 network namespaces
The most
On 17-01-2007 15:12, Michael Tokarev wrote:
Herbert Xu wrote:
On Tue, Jan 16, 2007 at 11:08:51AM +0300, Michael Tokarev wrote:
Ok. Here's another trace, from that remote network that triggers
this thing more-or-less reliable (every 2nd transfer at least) --
Jarek Poplawski wrote:
Here is my patch proposal. If I'm not totally wrong,
there is a possibility that, during collapsing, empty
skb with FIN is added to normal packet and changes
its ip_summed field to CHECKSUM_NONE.
diff -Nurp linux-2.6.19-/net/ipv4/tcp_output.c
Russell Stuart wrote:
On Thu, 2007-01-18 at 12:37 +0100, Patrick McHardy wrote:
Or are you proposing tc behave differently on different
kernel versions. (I have no problem with that, but
isn't it officially frowned upon?)
Yes. There is no way you can make this work on old kernels,
nobody
On Thu, Jan 18, 2007 at 08:55:37AM -0500, Brandon Craig Rhodes wrote:
to debugging messages! In some circumstances, debug messages are
always produced; in several others, net_ratelimit() is called to
decided whether to print an error (but why in these cases and not
others?); and in many
MultiTCP[1] is (yet another) Linux TCP patch intended for
researchers/developers, which can report TCP events in the kernel logs
in order to watch TCP internal variables.
Furthermore, it includes TCP Pacing and Hoe's initial ssthresh
estimation[2]. Their use in satellite links is strongly
Jarek Poplawski wrote:
On 17-01-2007 15:12, Michael Tokarev wrote:
[]
Here's another sample, which may be more useful. I've seen quite
alot of very similar stuff while running tcpdump.
http://www.corpit.ru/mjt/bad-cksum-session3-dmp.bin
The scenario looks like this.
A client
Patrick McHardy wrote:
Jarek Poplawski wrote:
Here is my patch proposal. If I'm not totally wrong,
there is a possibility that, during collapsing, empty
skb with FIN is added to normal packet and changes
its ip_summed field to CHECKSUM_NONE.
diff -Nurp linux-2.6.19-/net/ipv4/tcp_output.c
The sysfs patch broke using multiple instances of the bonding module
through module renaming (modprobe -o). In recent kernels it fails
with -EEXIST when trying to add the bonding_masters file for the
second time, in older kernels (where sysfs_add_file didn't check
for duplicates) it will crash
On Fri, Jan 19, 2007 at 04:20:01PM +0300, Michael Tokarev wrote:
...
Well.. I just tried it - with this patch applied, no more bad checksums
are shown. Tried from the network that triggers it most reliable - and
wasn't able to reproduce the bad behavior.
I'm running a tcpdump right now,
On Fri, Jan 19, 2007 at 01:14:52PM +0100, Patrick McHardy wrote:
Jarek Poplawski wrote:
Here is my patch proposal. If I'm not totally wrong,
there is a possibility that, during collapsing, empty
skb with FIN is added to normal packet and changes
its ip_summed field to CHECKSUM_NONE.
From: Daniel Lezcano [EMAIL PROTECTED]
Initialize the init's network namespace to level 2
Signed-off-by: Daniel Lezcano [EMAIL PROTECTED]
---
net/core/net_namespace.c |1 +
1 file changed, 1 insertion(+)
Index: 2.6.20-rc4-mm1/net/core/net_namespace.c
This patchset provide a network isolation similar at what
Linux-Vserver provides. It is based on the L2 namespaces and relies on
the mechanisms provided by the namespace. This L3 namespaces does not
aim to bring full virtualization for the network, it provides an IP
isolation which can be reused
From: Daniel Lezcano [EMAIL PROTECTED]
All L3 namespaces are the final nodes of the L2 namespaces
tree. Because their share some ressources coming from the L2
namespace. The L2 parent namespace should be stored into the L3 child
when it is created.
Signed-off-by: Daniel Lezcano [EMAIL PROTECTED]
From: Daniel Lezcano [EMAIL PROTECTED]
Broadcast packets should be delivered to l2 and all l3 childs
Signed-off-by: Daniel Lezcano [EMAIL PROTECTED]
---
include/linux/net_namespace.h | 11 +++
net/core/net_namespace.c | 27 +++
net/ipv4/udp.c
From: Daniel Lezcano [EMAIL PROTECTED]
Switch to the the l3 namespace using the destination address.
Signed-off-by: Daniel Lezcano [EMAIL PROTECTED]
---
include/linux/net_namespace.h |7 +++
net/core/net_namespace.c | 35 +++
net/ipv4/ip_input.c
From: Daniel Lezcano [EMAIL PROTECTED]
Add a specific condition when doing inet interface listing
in order to see always the loopback address.
Signed-off-by: Daniel Lezcano [EMAIL PROTECTED]
---
include/linux/net_namespace.h |9 +
net/core/net_namespace.c | 22
From: Daniel Lezcano [EMAIL PROTECTED]
L3 namespace will use routes and devices belonging to its parent, so
the old network namespace structure is copied when allocating a new
one. By this way, hash value, dev list, routes are accessible from the
L3 namespaces. In case of L2 namespace, these
From: Daniel Lezcano [EMAIL PROTECTED]
Check the bind address is allowed. It must match ifaddr assigned to
the namespace and all derivative addresses.
Signed-off-by: Daniel Lezcano [EMAIL PROTECTED]
---
include/linux/net_namespace.h |7 +
net/core/net_namespace.c | 54
From: Daniel Lezcano [EMAIL PROTECTED]
When no source address is specified, search from the dev list the
ifaddr allowed to be used as source address.
Signed-off-by: Daniel Lezcano [EMAIL PROTECTED]
---
include/linux/net_namespace.h | 14
net/core/net_namespace.c | 68
From: Daniel Lezcano [EMAIL PROTECTED]
When a packet is outgoing, the namespace source is stored
into the skbuff. Because it is the loopback address, the
source == destination, so when the packet is incoming, it
has already the namespace destination set into the packet.
Signed-off-by: Daniel
From: Daniel Lezcano [EMAIL PROTECTED]
New ioctl to push ifaddr to a container. Actually, the push is done
from the current namespace, so the right word is pull. That will be
changed to move ifaddr from l2 network namespace to l3.
Signed-off-by: Daniel Lezcano [EMAIL PROTECTED]
---
From: Daniel Lezcano [EMAIL PROTECTED]
For debug purpose only, this is not intended to be included.
Add /sys/kernel/debug/net_ns.
Creation of network namespace:
echo level /sys/kernel/debug/net_ns/start
Signed-off-by: Daniel Lezcano [EMAIL PROTECTED]
---
fs/debugfs/Makefile |2
Hi Jeff,
Thanks for the comments and references.
As per you suggestion, we have resubmitted the patches with required
change.
Thanks,
~Siva
-Original Message-
From: Jeff Garzik [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 18, 2007 10:32 PM
To: Ananda Raju
Cc:
On Fri, Jan 19, 2007 at 11:57:00AM +0530, Suparna Bhattacharya ([EMAIL
PROTECTED]) wrote:
Since you are implementing new APIs here, have you considered doing an
aio_sendfilev to be able to send a header with the data ?
It is doable, but why people do not like corking?
With Linux less
Let me briefly describe your approach and possible drawbacks in it.
You start reserving some memory when systems is under memory pressure.
when system is in real trouble, you start using that reserve for special
tasks mainly for network path to allocate packets and process them in
order to
On Thu, Jan 18, 2007 at 09:22:52PM +, Andrew Walrond wrote:
Don't know exactly when this change went in, but it's not in 2.6.18.3
and is in 2.6.19.2+
$ diff linux/include/linux/if_arp.h linux-2.6/include/linux/if_arp.h
133,134c133,134
unsigned short ar_hrd; /* format
On Thu, 18 Jan 2007, Peter Zijlstra wrote:
Cache misses for small packet flow due to the fact, that the same data
is allocated and freed and accessed on different CPUs will become an
issue soon, not right now, since two-four core CPUs are not yet to be
very popular and price for the
On Fri, Jan 19, 2007 at 12:06:41PM +0100, Jarek Poplawski wrote:
[PATCH][NET] tcp_output: rare bad TCP checksum with 2.6.19
The patch Replace CHECKSUM_HW by CHECKSUM_PARTIAL/CHECKSUM_COMPLETE
changed to unconditional copying of ip_summed field from collapsed
skb. This patch reverts this
Patch to Implement IPv6 RFC 4429 (Optimistic Duplicate Address Detection). In
short, this is a feature whereby a node with a Tentative address can begin to
make use of that address almost immediately after its configured. To enable
this, extra rules need to be followed during the Duplicate
Jeff Garzik wrote:
Ayaz Abdulla wrote:
This patch adds a limit to how much tx work can be done in each
iteration of tx processing.
Signed-Off-By: Ayaz Abdulla [EMAIL PROTECTED]
What about the tail end of the work, when the limit is reached?
Remember that delaying the completion of TX's
Patrick McHardy [EMAIL PROTECTED] wrote:
The sysfs patch broke using multiple instances of the bonding module
through module renaming (modprobe -o). In recent kernels it fails
with -EEXIST when trying to add the bonding_masters file for the
second time, in older kernels (where sysfs_add_file
e1000: update device ID table for register dumps with new devices
From: Auke Kok [EMAIL PROTECTED]
The register dump routine of e1000 was missing several newer chipsets. I
reimported the mac detection code from the linux e1000 driver. This fixes
newer NIC's reporting that their bus type is PCI
Hello.
In article [EMAIL PROTECTED] (at Fri, 19 Jan 2007 16:23:14 -0500), Neil
Horman [EMAIL PROTECTED] says:
Patch to Implement IPv6 RFC 4429 (Optimistic Duplicate Address Detection). In
Good work. We will see if this would break core and basic ipv6 code.
Dave, please hold on.
Some quick
Auke Kok wrote:
e1000: update device ID table for register dumps with new devices
From: Auke Kok [EMAIL PROTECTED]
The register dump routine of e1000 was missing several newer chipsets. I
reimported the mac detection code from the linux e1000 driver. This fixes
newer NIC's reporting that their
On Fri, Jan 19, 2007 at 01:53:15PM +0100, Peter Zijlstra ([EMAIL PROTECTED])
wrote:
2. You differentiate by hand between critical and non-critical
allocations by specifying some kernel users as potentially possible to
allocate from reserve.
True, all sockets that are needed for swap,
Auke Kok wrote:
Adam Kropelin wrote:
I am experiencing the no-link issue on a 82572EI single port copper
PCI-E card. I've only tried 2.6.20-rc5, so I cannot tell if this is a
regression or not yet. Will test older kernel soon.
Can provide details/logs if you want 'em.
we've already
Adam Kropelin wrote:
Auke Kok wrote:
Adam Kropelin wrote:
I am experiencing the no-link issue on a 82572EI single port copper
PCI-E card. I've only tried 2.6.20-rc5, so I cannot tell if this is a
regression or not yet. Will test older kernel soon.
Can provide details/logs if you want 'em.
Auke Kok wrote:
Adam Kropelin wrote:
I haven't been able to test rc5-mm yet because it won't boot on this
box. Applying git-e1000 directly to -rc4 or -rc5 results in a number
of rejects that I'm not sure how to fix. Some are obvious, but the
others I'm unsure of.
that won't work. You either
Adam Kropelin wrote:
Auke Kok wrote:
Adam Kropelin wrote:
I haven't been able to test rc5-mm yet because it won't boot on this
box. Applying git-e1000 directly to -rc4 or -rc5 results in a number
of rejects that I'm not sure how to fix. Some are obvious, but the
others I'm unsure of.
that
On Sat, Jan 20, 2007 at 08:05:07AM +0900, YOSHIFUJI Hideaki / 吉藤英明 wrote:
Hello.
In article [EMAIL PROTECTED] (at Fri, 19 Jan 2007 16:23:14 -0500), Neil
Horman [EMAIL PROTECTED] says:
Patch to Implement IPv6 RFC 4429 (Optimistic Duplicate Address Detection).
In
Good work. We will
The code to select names for the bonding interfaces was, for the
non-sysfs creation case, always using a hard-coded set of bond0, bond1,
etc, up to max_bonds. This caused conflicts for the second or
subsequent loads of the module.
Changed the code to obtain device names from
The existing code did not correctly handle failures to create
the per-interface sysfs group for bonding.
Modified code to notice errors, and correctly unwind.
Signed-off-by: Jay Vosburgh [EMAIL PROTECTED]
diff --git a/drivers/net/bonding/bond_main.c
Update version number to reflect recent changes.
Signed-off-by: Jay Vosburgh [EMAIL PROTECTED]
diff --git a/drivers/net/bonding/bonding.h b/drivers/net/bonding/bonding.h
index dc434fb..6123b90 100644
--- a/drivers/net/bonding/bonding.h
+++ b/drivers/net/bonding/bonding.h
@@ -22,8 +22,8
Patch 1: fix device name allocation error
Patch 2: fix error check in sysfs creation
Patch 3: modify sysfs support to permit multiple loads
Patch 4: update version number
This patch series should resolve whatever problems there are
with the logic to load
The existing code would blindly attempt to create the
bonding_masters file (in /sys/class/net) every time the module was
loaded. When the module is loaded multiple times (which is the
historical method used by initscripts and sysconfig to create multiple
bonding interfaces), this caused
On Fri, 2007-01-19 at 13:19 +0100, Patrick McHardy wrote:
Russell Stuart wrote:
I thought that some degree of compatibility was
expected. At the very least the newest version
of tc must work on _any_ kernel as least as
well as the version it replaces did.
I also though newer
On Fri, Jan 19, 2007 at 04:47:22PM +0100, [EMAIL PROTECTED] wrote:
From: Daniel Lezcano [EMAIL PROTECTED]
Switch to the the l3 namespace using the destination address.
Signed-off-by: Daniel Lezcano [EMAIL PROTECTED]
---
include/linux/net_namespace.h |7 +++
On Fri, Jan 19, 2007 at 04:47:26PM +0100, [EMAIL PROTECTED] wrote:
From: Daniel Lezcano [EMAIL PROTECTED]
Broadcast packets should be delivered to l2 and all l3 childs
hmm, really? shouldn't it only reach those which
actually have related addresses assigned?
best,
Herbert
Signed-off-by:
On Fri, Jan 19, 2007 at 04:47:14PM +0100, [EMAIL PROTECTED] wrote:
This patchset provide a network isolation similar at what
Linux-Vserver provides. It is based on the L2 namespaces and relies on
the mechanisms provided by the namespace. This L3 namespaces does not
aim to bring full
On Fri, Jan 19, 2007 at 04:47:19PM +0100, [EMAIL PROTECTED] wrote:
From: Daniel Lezcano [EMAIL PROTECTED]
New ioctl to push ifaddr to a container. Actually, the push is done
from the current namespace, so the right word is pull. That will be
changed to move ifaddr from l2 network namespace
Hey Roland,
Jeff has pulled in the Chelsio Ethernet driver. If you are ready to
merge in the RDMA driver, you can pull it from
git://staging.openfabrics.org/~swise/cxgb3.git for-roland
Thanks,
Steve.
Forwarded Message
From: Jeff Garzik [EMAIL PROTECTED]
To: Divy Le Ray
Jeff has pulled in the Chelsio Ethernet driver. If you are ready to
merge in the RDMA driver, you can pull it from
Yes, I saw that... OK, I'll get serious about reviewing the RDMA stuff.
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL
54 matches
Mail list logo
