On Sunday 10 June 2007 03:52, Jeff Garzik wrote:
Mithlesh Thukral wrote:
- if ((netif_running(netdev)) !netif_carrier_ok(netdev)) {
- printk(KERN_INFO %s port %d, %s carrier is now ok\n,
- netxen_nic_driver_name, adapter-portnum, netdev-name);
+ if
On Fri, Jun 08 2007, Evgeniy Polyakov wrote:
Size of the received file is bigger than file sent, file contains repeated
blocks of data sometimes. Cloned skb usage is likely too big overhead,
although for receiving fast clone is unused in most cases, so there
might be some gain.
That was
[CC'd Al Viro and Alan Cox, restored patch]
There are races involving the garbage collector, that can throw away
perfectly good packets with AF_UNIX sockets in them.
The problems arise when a socket goes from installed to in-flight or
vice versa during garbage collection. Since gc is
Hi All,
I will be resending the patches related to link status and multicast
filter of NetXen's 1/10G Ethernet driver code after incorporating
the feedback which we got.
These patches are wrt netdev#upstream-fixes.
Regards,
Mithlesh Thukral
-
To unsubscribe from this list: send the line
NetXen: Fix incorrect link status even with switch turned OFF.
NetXen driver failed to accurately indicate when a link is up or down.
This was encountered during failover testing, when the first port
indicated that the link was up even when the 10G switch it was assigned
to in the Bladecenter
NetXen: Add multi cast filter code
This patch adds multi cast filter code to NetXen NIC driver.
It also adds capabilities to setup the multicast address in hardware
from the host side.
Signed-off by: Mithlesh Thukral [EMAIL PROTECTED]
---
drivers/net/netxen/netxen_nic.h | 24
Hi Dave,
I am sorry to miss out during Jamal's original effort to make
qdisc_restart more readable, but I feel some more changes could
help in that direction. Plus there were some useful comments
in the original code which I updated (hopefully correctly) and
put back - it does seem useful for a
David Miller wrote:
Get it while it's hot:
kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.23.git
We have the qdisc_restart cleanup from Jama, some TIPC work
from Allan Stephens and co., and Patrick's rtnl_link work.
I hope this still gives me the chance to submit updated
Pavel Emelianov wrote:
Patrick McHardy wrote:
+skb-pkt_type = PACKET_HOST;
+skb-protocol = eth_type_trans(skb, rcv);
+if (dev-features NETIF_F_NO_CSUM)
+skb-ip_summed = rcv_priv-ip_summed;
+
+dst_release(skb-dst);
+skb-dst = NULL;
+
+secpath_reset(skb);
+
Ben Greear wrote:
Pavel Emelianov wrote:
I would also like some way to identify veth from other device types,
preferably
something like a value in sysfs. However, that should not hold up
We can do this with ethtool. It can get and print the driver name of
the device.
I
jamal wrote:
On Wed, 2007-06-06 at 17:11 +0200, Patrick McHardy wrote:
[...]
The problem is the premise is _innacurate_.
Since you havent followed the discussion, i will try to be brief (which
is hard).
If you want verbosity it is in my previous emails:
Consider a simple example of
Hi,
Here's an updated implementation of tcp network splice receive support.
It actually works for me now, no data corruption seen.
For the original announcement and how to test it, see:
http://marc.info/?l=linux-netdevm=118103093400770w=2
I hang on to the original skb by creating a clone of it
jamal wrote:
On Wed, 2007-06-06 at 15:35 -0700, David Miller wrote:
The problem with this line of thinking is that it ignores the fact
that it is bad to not queue to the device when there is space
available, _even_ for lower priority packets.
So use a different scheduler. Dont use strict
Waskiewicz Jr, Peter P wrote:
If they have multiple TX queues, independantly programmable, that
single lock is stupid.
We could use per-queue TX locks for such hardware, but we can't
support that currently.
There could be bad packet reordering with this (like some SMP
routers used to do).
On Mon, 2007-11-06 at 13:58 +0200, Patrick McHardy wrote:
Thats not true. Assume PSL has lots of packets, PSH is empty. We
fill the PHL queue until their is no room left, so the driver
has to stop the queue.
Sure. Packets stashed on the any DMA ring are considered gone to the
wire. That is a
Herbert Xu wrote:
[IPV4]: Add default config support after inetdev_init
Previously once inetdev_init has been called on a device any changes made
to ipv4_devconf_dflt would have no effect on that device's configuration.
I noticed a few more side-effects from the original change that
seem to
On Mon, Jun 11, 2007 at 02:26:58PM +0200, Patrick McHardy wrote:
I noticed a few more side-effects from the original change that
seem to be undesired. Some code assumes that dev-ip_ptr != NULL
implies existance of IP addresses on the device. For example
fib_check_nh used to allow to add
Ben Greear wrote:
This should also be useful with the pending 'veth' driver, as it
emulates two ethernet ports connected with a cross-over cable.
To make this work, you have to enable the sysctl (look Dave,
no IOCTLS, there might be hope for me yet!! :)), and in your
application you will
jamal wrote:
On Mon, 2007-11-06 at 13:58 +0200, Patrick McHardy wrote:
Thats not true. Assume PSL has lots of packets, PSH is empty. We
fill the PHL queue until their is no room left, so the driver
has to stop the queue.
Sure. Packets stashed on the any DMA ring are considered gone to
On Mon, 2007-11-06 at 14:39 +0200, Patrick McHardy wrote:
jamal wrote:
On Mon, 2007-11-06 at 13:58 +0200, Patrick McHardy wrote:
Sure. Packets stashed on the any DMA ring are considered gone to the
wire. That is a very valid assumption to make.
I disagree, its obviously not true
jamal wrote:
On Mon, 2007-11-06 at 14:39 +0200, Patrick McHardy wrote:
Sure. Packets stashed on the any DMA ring are considered gone to the
wire. That is a very valid assumption to make.
I disagree, its obviously not true
Patrick, you are making too strong a statement.
Well, its not.
On Mon, 2007-11-06 at 15:03 +0200, Patrick McHardy wrote:
jamal wrote:
Well, its not.
I dont wanna go into those old style debates again; so lets drop this
point.
Take a step back:
When you put a packet on the DMA ring, are you ever going to take it
away at some point before it goes to
I have started writting a small howto for drivers. Hoping to get a wider
testing with more drivers.
So far i have changed e1000 and tun drivers as well as modified the
packetgen tool to do batching.
I will update this document as needed if something is unclear.
Please contribute by asking
jamal wrote:
On Mon, 2007-11-06 at 15:03 +0200, Patrick McHardy wrote:
Take a step back:
When you put a packet on the DMA ring, are you ever going to take it
away at some point before it goes to the wire?
No, but its nevertheless not on the wire yet and the HW scheduler
controls when it will
Patrick McHardy wrote:
jamal wrote:
Sure - but what is wrong with that?
Nothing, this was just to illustrate why I disagree with the
assumption
that the packet has hit the wire. On second thought I do agree with
your
assumption for the single HW queue case, at the point we hand the
On Mon, 2007-11-06 at 16:03 +0200, Patrick McHardy wrote:
jamal wrote:
Sure - but what is wrong with that?
Nothing, this was just to illustrate why I disagree with the assumption
that the packet has hit the wire.
fair enough.
On second thought I do agree with your
assumption for the
Cohen, Guy wrote:
Patrick McHardy wrote:
jamal wrote:
Sure - but what is wrong with that?
Nothing, this was just to illustrate why I disagree with the
assumption
that the packet has hit the wire. On second thought I do agree with
your
assumption for the single HW queue case, at the
On Mon, 2007-11-06 at 17:30 +0300, Cohen, Guy wrote:
For WiFi devices the HW often implements the scheduling, especially when
QoS (WMM/11e/11n) is implemented. There are few traffic queues defined
by the specs and the selection of the next queue to transmit a packet
from, is determined in
jamal wrote:
On Mon, 2007-11-06 at 16:03 +0200, Patrick McHardy wrote:
Read again what I wrote about the n 2 case. Low priority queues might
starve high priority queues when using a single queue state for a
maximum of the time it takes to service n - 2 queues with max_qlen - 1
packets queued
On 6/11/07, jamal [EMAIL PROTECTED] wrote:
On Mon, 2007-11-06 at 17:30 +0300, Cohen, Guy wrote:
For WiFi devices the HW often implements the scheduling, especially when
QoS (WMM/11e/11n) is implemented. There are few traffic queues defined
by the specs and the selection of the next queue to
On Mon, 2007-11-06 at 16:49 +0200, Patrick McHardy wrote:
Let me explain with some ASCII art :)
Ok ;-
We have n empty HW queues with a maximum length of m packets per queue:
[0] empty
[1] empty
[2] empty
..
[n-1] empty
Asumming 0 i take it is higher prio than n-1.
Now we receive
On Mon, 2007-11-06 at 18:00 +0300, Tomas Winkler wrote:
On 6/11/07, jamal [EMAIL PROTECTED] wrote:
On Mon, 2007-11-06 at 17:30 +0300, Cohen, Guy wrote:
For WiFi devices the HW often implements the scheduling, especially when
QoS (WMM/11e/11n) is implemented. There are few traffic
jamal wrote:
On Mon, 2007-11-06 at 16:49 +0200, Patrick McHardy wrote:
We have n empty HW queues with a maximum length of m packets per queue:
[0] empty
[1] empty
[2] empty
..
[n-1] empty
Asumming 0 i take it is higher prio than n-1.
Yes.
Now we receive m - 1 packets for each all
On Mon, 2007-11-06 at 17:12 +0200, Patrick McHardy wrote:
Ok, so let me revert that; 0 is higher prio than n-1.
Yes.
Ok, gotcha.
possibly long time is where we diverge ;-
Worst cast is (n - 2) * (m - 1) + 1 full sized packet transmission
times.
You can do the math yourself,
On Sat, 2007-05-05 at 00:52 +0200, matthieu castet wrote:
Hi,
I attach a diff against 2.6.21 for adding wpa support for airo driver.
In then end of 2005 I manage to make work wpa but the code was really
ugly. I manage to find some time to clean it.
To support wpa, a new interface of
Some more details inside regarding wireless QoS.
jamal wrote:
On Mon, 2007-11-06 at 17:30 +0300, Cohen, Guy wrote:
For WiFi devices the HW often implements the scheduling, especially
when
QoS (WMM/11e/11n) is implemented. There are few traffic queues
defined
by the specs and the
jamal wrote:
On Mon, 2007-11-06 at 17:12 +0200, Patrick McHardy wrote:
Worst cast is (n - 2) * (m - 1) + 1 full sized packet transmission
times.
You can do the math yourself, but we're talking about potentially
a lot of packets.
I agree if you use the strategy of a ring shutdown down
Patrick McHardy wrote:
Ben Greear wrote:
This should also be useful with the pending 'veth' driver, as it
emulates two ethernet ports connected with a cross-over cable.
To make this work, you have to enable the sysctl (look Dave,
no IOCTLS, there might be hope for me yet!! :)), and in your
On Jun 6, 2007, at 4:28 AM, Milton Miller wrote:
On Jun 5, 2007, at 9:26 PM, Kok, Auke wrote:
Kok, Auke wrote:
Hmm git-revert seems to do the job right. I checked it with git-show
| patch -p1 -R and the results look OK. The two patches on top of
the one we want to revert are unrelated
Ben Greear wrote:
Patrick McHardy wrote:
I would really prefer to simply make the prio 0 lookup local
rule deletable so you can rules with higher priority. That
allows to do send to self without any further code changes
and avoids the need to bind applications to a device.
I am not
Stephen Hemminger wrote:
On Fri, 08 Jun 2007 16:42:31 -0700
Kok, Auke [EMAIL PROTECTED] wrote:
Stephen Hemminger wrote:
+#define ndev_printk(kern_level, netif_level, netdev, format, arg...) \
+ do { if ((netdev)-msg_enable NETIF_MSG_##netif_level) { \
+
PJ Waskiewicz wrote:
diff --git a/net/sched/sch_generic.c b/net/sched/sch_generic.c
index f28bb2d..b9dc2a6 100644
--- a/net/sched/sch_generic.c
+++ b/net/sched/sch_generic.c
@@ -123,7 +123,8 @@ static inline int qdisc_restart(struct net_device *dev)
/* And release queue
On Mon, 11 Jun 2007 10:30:26 -0700
Kok, Auke [EMAIL PROTECTED] wrote:
Stephen Hemminger wrote:
On Fri, 08 Jun 2007 16:42:31 -0700
Kok, Auke [EMAIL PROTECTED] wrote:
Stephen Hemminger wrote:
+#define ndev_printk(kern_level, netif_level, netdev, format, arg...) \
+do { if
PJ Waskiewicz wrote:
diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
index e7367c7..8bcd870 100644
--- a/include/linux/skbuff.h
+++ b/include/linux/skbuff.h
@@ -215,6 +215,7 @@ typedef unsigned char *sk_buff_data_t;
* @pkt_type: Packet class
* @fclone: skbuff clone
PJ Waskiewicz wrote:
diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h index
e7367c7..8bcd870 100644
--- a/include/linux/skbuff.h
+++ b/include/linux/skbuff.h
@@ -215,6 +215,7 @@ typedef unsigned char *sk_buff_data_t;
* @pkt_type: Packet class
* @fclone: skbuff clone
PJ Waskiewicz wrote:
diff --git a/net/sched/sch_generic.c
b/net/sched/sch_generic.c index
f28bb2d..b9dc2a6 100644
--- a/net/sched/sch_generic.c
+++ b/net/sched/sch_generic.c
@@ -123,7 +123,8 @@ static inline int qdisc_restart(struct
net_device *dev)
/* And
Waskiewicz Jr, Peter P wrote:
I think we can reuse skb-priority. Assuming only real
hardware devices use multiqueue support, there should be no user of
skb-priority after egress qdisc classification. The only reason
to preserve it in the qdisc layer is for software devices.
That would be
Waskiewicz Jr, Peter P wrote:
BTW, I couldn't find anything but a single
netif_wake_subqueue in your (old) e1000 patch. Why doesn't it
stop subqueues?
A previous e1000 patch stopped subqueues. The last e1000 patch I sent
to the list doesn't stop them, and that's a problem with that patch;
On Fri, Jun 08, 2007 at 01:20:20PM -0400, Jeff Garzik wrote:
On Fri, Jun 08, 2007 at 12:06:08PM -0500, Linas Vepstas wrote:
On Fri, Jun 08, 2007 at 11:12:31AM +1000, Michael Ellerman wrote:
On Thu, 2007-06-07 at 14:17 -0500, Linas Vepstas wrote:
The major bug fixes are:
I
I think grepping will help more than testing :)
The only issue I can see is that packets going to a
multiqueue device that doesn't have a multiqueue aware qdisc
attached will get a random value. So you would have to
conditionally reset it before -enqueue.
I currently clear queue_mapping
Avoid kernel crash in mm/slab.c due to double-free of pointer.
If the ethernet interface is brought down while there is still
RX traffic in flight, the device shutdown routine can end up
trying to double-free an skb, leading to a crash in mm/slab.c
Avoid the double-free by nulling out the skb
The terminated RX ring will cause trouble during the RX ram full
conditions, leading to a hung driver, as the hardware can't find
the next descr. There is no real reason to terminate the RX ring;
it doesn't make the operation any smooother, and it does
require an extra sync. So don't do it.
Hi Jeff,
Here are 3 minor updates of myri10ge for 2.6.22. The first one is a
reduced version of the earlier nacked patch, it now limits the number of
recoveries (to detect bad nics) without making the limit tunable.
1. limit the number of recoveries
2. report when the link partner is running in
Limit the number of recoveries from a NIC hw watchdog reset to 1 by default.
It enables detection of defective NICs immediately since these memory parity
errors are expected to happen very rarely (less than once per century*NIC).
Signed-off-by: Brice Goglin [EMAIL PROTECTED]
---
Since Myri-10G boards may also run in Myrinet mode instead of Ethernet,
add a message when we detect that the link partner is not running in the
right mode.
Signed-off-by: Brice Goglin [EMAIL PROTECTED]
---
drivers/net/myri10ge/myri10ge.c | 15 ++-
1 file changed, 10 insertions(+),
Waskiewicz Jr, Peter P wrote:
Another question is what to do about other hard_start_xmit callers.
Independant of which field is used, should the classification
that may have happend on a different device be retained (TC
actions again)?
[...] Either way, before it gets enqueued through
Update myri10ge driver version to 1.3.1-1.248.
Signed-off-by: Brice Goglin [EMAIL PROTECTED]
---
drivers/net/myri10ge/myri10ge.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-rc/drivers/net/myri10ge/myri10ge.c
Although the previous patch resolved issues with hangs when the
RX ram full interrupt is encountered, there are still situations
where lots of RX ramfull interrupts arrive, resulting in a noisy
log in syslog. There is no need for this.
Signed-off-by: Linas Vepstas [EMAIL PROTECTED]
At some point, the transmit descriptor chain end interrupt (TXDCEINT)
was turned on. This is a mistake; and it damages small packet
transmit performance, as it results in a huge storm of interrupts.
Turn it off.
Signed-off-by: Linas Vepstas [EMAIL PROTECTED]
drivers/net/spider_net.h |
This patch fixes a rare deadlock that can occur when the kernel
is not able to empty out the RX ring quickly enough. Below follows
a detailed description of the bug and the fix.
As long as the OS can empty out the RX buffers at a rate faster than
the hardware can fill them, there is no problem.
From: Florin Malita [EMAIL PROTECTED]
The stats update code in spider_net_pass_skb_up() is touching the skb
after it's been passed up to the stack. To avoid that, just update the
stats first.
Signed-off-by: Florin Malita [EMAIL PROTECTED]
Signed-off-by: Linas Vepstas [EMAIL PROTECTED]
Use dev_err() to print device error messages.
Signed-off-by: Linas Vepstas [EMAIL PROTECTED]
drivers/net/spider_net.c | 64 ---
1 file changed, 34 insertions(+), 30 deletions(-)
Index: linux-2.6.22-rc1/drivers/net/spider_net.c
Crazy device problems are hard to debug, when one does not have
good trace info. This patch makes a major enhancement to the
device dump routine.
Signed-off-by: Linas Vepstas [EMAIL PROTECTED]
drivers/net/spider_net.c | 78 ++-
1 file changed,
Invalidate a pointer as its pci_unmap'ed; this is a bit of
paranoia to make sure hardware doesn't continue trying to
DMA to it.
Signed-off-by: Linas Vepstas [EMAIL PROTECTED]
drivers/net/spider_net.c |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
Index:
On Jun 11, 2007, at 02:53, Mark Zhan wrote:
Current MII bitbang bus driver hard-codes the phy mask of mii_bus to
~0x09, which is actually specific to the FSL boards. This patch will
make the bitbang driver to generate MII bus phy_mask dynamically,
by the
PHY irq info provided by the
On Mon, Jun 11, 2007 at 03:53:37PM +0800, Mark Zhan wrote:
Current MII bitbang bus driver hard-codes the phy mask of mii_bus to
~0x09, which is actually specific to the FSL boards. This patch will
make the bitbang driver to generate MII bus phy_mask dynamically, by the
PHY irq info provided by
When entering the netdev poll routine, empty out the RX
chain first, before cleaning up the TX chain. This should
help avoid RX buffer overflows.
Signed-off-by: Linas Vepstas [EMAIL PROTECTED]
drivers/net/spider_net.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index:
Another way of minimizing the likelyhood of RX ram from overflowing
is to empty out the entire rx ring every chance we get. Change
the crazy watchdog timeout from 50 seconds to 3 seconds, while
we're here.
Signed-off-by: Linas Vepstas [EMAIL PROTECTED]
drivers/net/spider_net.h |9
On Mon, Jun 11, 2007 at 03:53:37PM +0800, Mark Zhan wrote:
Current MII bitbang bus driver hard-codes the phy mask of mii_bus to
~0x09, which is actually specific to the FSL boards. This patch will
make the bitbang driver to generate MII bus phy_mask dynamically, by the
PHY irq info provided by
Put the enable and disable routines next to one-another,
as this makes verifying thier symmetry that much easier.
Signed-off-by: Linas Vepstas [EMAIL PROTECTED]
drivers/net/spider_net.c | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
Index:
The transmit frame tail bit is stranglely misnamed as
no checksum. Fix the name to what it should be:
transmit frame tail. No functional change,
just a name change.
Signed-off-by: Linas Vepstas [EMAIL PROTECTED]
drivers/net/spider_net.c |2 +-
drivers/net/spider_net.h |2 +-
2
Documentation for the spidernet driver.
Signed-off-by: Linas Vepstas [EMAIL PROTECTED]
Documentation/networking/spider_net.txt | 204
1 file changed, 204 insertions(+)
Index: linux-2.6.22-rc1/Documentation/networking/spider_net.txt
I like the ndev_printk idea.
I think a ndev_level printks should take a const netdev*
as the first argument.
Also, better for the non-debug use of ndev_dbg is to have a
static inline function so printf args are verified.
For instance, dev_dbg does:
static inline int __attribute__ ((format
We are doing pure IPv4 forwarding between two
Ethernet
interfaces:
IXIA port A---System Under Test---IXIA Port B
Traffic has two IP destinations for each direction
and
L4 protocol is UDP. There are two static ARP
entries
and only interface routes. Two tests are identical
Joe Perches wrote:
I like the ndev_printk idea.
I think a ndev_level printks should take a const netdev*
as the first argument.
Also, better for the non-debug use of ndev_dbg is to have a
static inline function so printf args are verified.
For instance, dev_dbg does:
static inline int
From: Patrick McHardy [EMAIL PROTECTED]
Date: Mon, 11 Jun 2007 13:12:08 +0200
I hope this still gives me the chance to submit updated patches
since I've changed a few things since the last submission and
a single incremental update would mix things that don't really
belong together.
BTW,
David Miller wrote:
From: Patrick McHardy [EMAIL PROTECTED]
Date: Mon, 11 Jun 2007 13:12:08 +0200
I hope this still gives me the chance to submit updated patches
since I've changed a few things since the last submission and
a single incremental update would mix things that don't really
On Mon, 2007-11-06 at 17:44 +0200, Patrick McHardy wrote:
jamal wrote:
[..]
- let the driver shutdown whenever a ring is full. Remember which ring X
shut it down.
- when you get a tx interupt or prun tx descriptors, if a ring = X has
transmitted a packet (or threshold of packets), then
A lot of netdevices implement their own variant of printk and use
use variations of dev_printk, printk or others that use msg_enable,
which has been an eyesore with countless variations across drivers.
This patch implements a standard ndev_printk and derivatives
such as ndev_err, ndev_info,
With the generic ndev_printk macros, we can now convert network
drivers to use this generic printk family for netdevices.
Signed-off-by: Auke Kok [EMAIL PROTECTED]
---
drivers/net/e100.c| 135 -
drivers/net/e1000/e1000.h | 15
Auke Kok wrote:
A lot of netdevices implement their own variant of printk and use
use variations of dev_printk, printk or others that use msg_enable,
which has been an eyesore with countless variations across drivers.
snip
+#define ndev_err(netdev, level, format, arg...) \
+ do { if
On Mon, 2007-06-11 at 14:37 -0700, Auke Kok wrote:
diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
index 3a70f55..d185f41 100644
--- a/include/linux/netdevice.h
+++ b/include/linux/netdevice.h
@@ -540,6 +540,8 @@ struct net_device
struct device dev;
On Mon, 11 Jun 2007 14:37:21 -0700 Auke Kok wrote:
include/linux/netdevice.h | 38 ++
net/core/dev.c|5 +
net/core/ethtool.c| 14 +++---
3 files changed, 50 insertions(+), 7 deletions(-)
diff --git
Joe Perches wrote:
On Mon, 2007-06-11 at 14:37 -0700, Auke Kok wrote:
diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
index 3a70f55..d185f41 100644
--- a/include/linux/netdevice.h
+++ b/include/linux/netdevice.h
@@ -540,6 +540,8 @@ struct net_device
struct device
Randy Dunlap wrote:
On Mon, 11 Jun 2007 14:37:21 -0700 Auke Kok wrote:
include/linux/netdevice.h | 38 ++
net/core/dev.c|5 +
net/core/ethtool.c| 14 +++---
3 files changed, 50 insertions(+), 7 deletions(-)
diff
On Mon, 11 Jun 2007 14:37:21 -0700
Auke Kok [EMAIL PROTECTED] wrote:
A lot of netdevices implement their own variant of printk and use
use variations of dev_printk, printk or others that use msg_enable,
which has been an eyesore with countless variations across drivers.
This patch
On Mon, 2007-11-06 at 18:34 +0300, Cohen, Guy wrote:
jamal wrote:
[..]
WMM is a strict prio mechanism.
The parametrization very much favors the high prio packets when the
tx opportunity to send shows up.
Sorry, but this not as simple as you describe it. WMM is much more
complicated.
On Mon, 11 Jun 2007 12:05:02 -0700 (PDT)
Philip Romanov [EMAIL PROTECTED] wrote:
We are doing pure IPv4 forwarding between two
Ethernet
interfaces:
IXIA port A---System Under Test---IXIA Port B
Traffic has two IP destinations for each direction
and
L4 protocol is
On Mon, 2007-06-11 at 15:01 -0700, Kok, Auke wrote:
msg_enable is more frequently defined in drivers/net as u32 not int.
yes, we're only using the bottom 15 bits anyway, but the net_device struct
consistently uses 'int' style members, leaving it up to the compiler to pick
an
appropriate
Stephen Hemminger wrote:
On Mon, 11 Jun 2007 14:37:21 -0700
Auke Kok [EMAIL PROTECTED] wrote:
A lot of netdevices implement their own variant of printk and use
use variations of dev_printk, printk or others that use msg_enable,
which has been an eyesore with countless variations across
jamal wrote:
On Mon, 2007-11-06 at 17:44 +0200, Patrick McHardy wrote:
jamal wrote:
[..]
- let the driver shutdown whenever a ring is full. Remember which ring X
shut it down.
- when you get a tx interupt or prun tx descriptors, if a ring = X has
transmitted a packet (or threshold of
A small update on the e1000
On Mon, 2007-11-06 at 09:52 -0400, jamal wrote:
I have started writting a small howto for drivers. Hoping to get a wider
testing with more drivers.
So far i have changed e1000 and tun drivers as well as modified the
packetgen tool to do batching.
I will
A lot of netdevices implement their own variant of printk and use
use variations of dev_printk, printk or others that use msg_enable,
which has been an eyesore with countless variations across drivers.
This patch implements a standard ndev_printk and derivatives
such as ndev_err, ndev_info,
jamal wrote:
On Mon, 2007-11-06 at 17:44 +0200, Patrick McHardy wrote:
At this point the qdisc might send new packets. What do you do when a
packet for a full ring arrives?
Hrm... ok, is this a trick question or i am missing the obvious?;-
What is wrong with what any driver would do
Dave,
Here are a few mac80211 patches appropriate for 2.6.22.
Individual patches to follow, or you can pull at your leisure...
John
---
The following changes since commit 5ecd3100e695228ac5e0ce0e325e252c0f11806f:
Linus Torvalds (1):
Linux 2.6.22-rc4
are found in the git repository
Dave,
Here are a few mac80211 patches appropriate for 2.6.23.
Individual patches to follow, or you can pull at your leisure...
John
---
The following changes since commit 5ecd3100e695228ac5e0ce0e325e252c0f11806f:
Linus Torvalds (1):
Linux 2.6.22-rc4
are found in the git repository
From: Johannes Berg [EMAIL PROTECTED]
This patch fixes a typo in mac80211's debugfs.c.
Signed-off-by: Johannes Berg [EMAIL PROTECTED]
Signed-off-by: John W. Linville [EMAIL PROTECTED]
---
net/mac80211/debugfs.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
From: David Lamparter [EMAIL PROTECTED]
Fix signedness mixup making mac addresses show up strangely
(like 00:11:22:33:44:ffaa) in /sys/class/ieee80211/*/macaddress.
Signed-off-by: David Lamparter [EMAIL PROTECTED]
Acked-by: Johannes Berg [EMAIL PROTECTED]
Signed-off-by: John W. Linville
From: Mattias Nissler [EMAIL PROTECTED]
mac80211 stops the tx queues during scans. This is wrong with respect
to the master deivce tx queue, since stopping it prevents any probes
from being sent during the scan. Instead, they accumulate in the queue
and are only sent after the scan is finished,
From: Larry Finger [EMAIL PROTECTED]
The initial rate for STA's using rc80211_simple is set to the last
rate in the rate table. For situations for which the signal is weak,
the rate may be too high for authentication and association. Although
the rc80211_simple module will adjust the speed, the
1 - 100 of 107 matches
Mail list logo
