From: Jeff Kirsher <jeffrey.t.kirsher@intel.com> Applied, thanks guys. --

From: Alexander Duyck <alexander.h.duyck@intel.com> Add support for multiq qdisc This patch adds the ability to configure the multiq qdisc. Since the qdisc does not require any input it will pull the number of bands directly from the device that it is added to the root of. usage: tc qdisc add dev <DEV> root handle <HANDLE> multiq Signed-off-by: Alexander Duyck <alexander.h.duyck@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com> --- include/linux/pkt_sched.h | 7 ...

On Fri, 5 Dec 2008, Ben Hutchings wrote: > On Fri, 2008-12-05 at 23:43 +0200, Ilpo J

1) Some fixes to recent work, and some to pre-historic things. 2) sacktag state struct to avoid ..., *ptr, *ptr2, *ptr3 crazyness 3) Besides that combine some code here and there. -- i. --

tcp_minshall_update is not significant difference since it only checks for not full-sized skb which is BUG'ed one the push_one path anyway. tcp_snd_test is tcp_nagle_test+tcp_cwnd_test+tcp_snd_wnd_test, just the order changed slightly. net/ipv4/tcp_output.c: tcp_snd_test | -89 tcp_mss_split_point | -91 tcp_may_send_now | +53 tcp_cwnd_validate | -98 tso_fragment | -239 __tcp_push_pending_frames | -1340 tcp_push_one ...

Also make if-goto forest nicer looking. Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> --- net/ipv4/tcp_input.c | 9 ++++----- 1 files changed, 4 insertions(+), 5 deletions(-) diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c index d67b6e9..63c3ef6 100644 --- a/net/ipv4/tcp_input.c +++ b/net/ipv4/tcp_input.c @@ -1575,11 +1575,10 @@ static struct sk_buff *tcp_shift_skb_data(struct sock *sk, struct sk_buff *skb, goto out; skb = tcp_write_queue_next(sk, prev); ...

Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> --- net/ipv4/tcp_output.c | 23 ++++++++++++----------- 1 files changed, 12 insertions(+), 11 deletions(-) diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c index 0744b9f..59505ce 100644 --- a/net/ipv4/tcp_output.c +++ b/net/ipv4/tcp_output.c @@ -1527,13 +1527,6 @@ static int tcp_write_xmit(struct sock *sk, unsigned int mss_now, int nonagle) int cwnd_quota; int result; - /* If we are closed, the bytes will have to ...

Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> --- net/ipv4/tcp_input.c | 17 ++++++++++------- 1 files changed, 10 insertions(+), 7 deletions(-) diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c index 7d887ac..e379af9 100644 --- a/net/ipv4/tcp_input.c +++ b/net/ipv4/tcp_input.c @@ -3052,6 +3052,13 @@ static void tcp_fastretrans_alert(struct sock *sk, int pkts_acked, int flag) tcp_xmit_retransmit_queue(sk); } +static void tcp_valid_rtt_meas(struct sock *sk, u32 ...

Since jiffies is unsigned long, the types get expanded into that and after long enough time the difference will therefore always be > 1 (and that probably happens near boot as well as iirc the first jiffies wrap is scheduler close after boot to find out problems related to that early). This was originally noted by Bill Fink in Dec'07 but nobody never ended fixing it. Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> Cc: Bill Fink <billfink@mindspring.com> --- net/ipv4/tcp_output.c ...

Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- Documentation/wimax/README.wimax | 81 ++++++++++++++++++++++++++++++++++++++ 1 files changed, 81 insertions(+), 0 deletions(-) create mode 100644 Documentation/wimax/README.wimax diff --git a/Documentation/wimax/README.wimax b/Documentation/wimax/README.wimax new file mode 100644 index 0000000..b78c437 --- /dev/null +++ b/Documentation/wimax/README.wimax @@ -0,0 +1,81 @@ + + Linux kernel WiMAX stack + + (C) 2008 ...

Implements data transmission to the device; this is done through a software FIFO, as data/control frames can be coalesced (while the device is reading the previous tx transaction, others accumulate). A FIFO is used because at the end it is resource-cheaper that trying to implement scatter/gather over USB. As well, most traffic is going to be download (vs upload). Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- drivers/net/wimax/i2400m/tx.c | 817 ...

This defines the structures and constants for the host-device protocols: - boot / firmware upload protocol - general data transport protocol - control protocol This header file is done in such a way that can also be used verbatim by user space. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- include/linux/wimax/i2400m.h | 512 ++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 512 insertions(+), 0 deletions(-) create mode 100644 ...

This code implements reading from the SDIO device; when data is ready the SDIO IRQ is fired and that will allocate an skb, put all the data there and then pass it to the generic driver for processing and delivery. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- drivers/net/wimax/i2400m/sdio-rx.c | 255 ++++++++++++++++++++++++++++++++++++ 1 files changed, 255 insertions(+), 0 deletions(-) create mode 100644 drivers/net/wimax/i2400m/sdio-rx.c diff --git ...

This implements the backends for the generic driver (i2400m) to be able to load firmware to the SDIO device. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- drivers/net/wimax/i2400m/sdio-fw.c | 224 ++++++++++++++++++++++++++++++++++++ 1 files changed, 224 insertions(+), 0 deletions(-) create mode 100644 drivers/net/wimax/i2400m/sdio-fw.c diff --git a/drivers/net/wimax/i2400m/sdio-fw.c b/drivers/net/wimax/i2400m/sdio-fw.c new file mode 100644 index 0000000..3487205 --- ...

This patch adds entries for the original developers of the i2400m drivers and up-to-date maintainer entries. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- CREDITS | 17 +++++++++++++++++ MAINTAINERS | 16 ++++++++++++++++ 2 files changed, 33 insertions(+), 0 deletions(-) diff --git a/CREDITS b/CREDITS index b50db17..ae5b804 100644 --- a/CREDITS +++ b/CREDITS @@ -464,6 +464,11 @@ S: 1200 Goldenrod Dr. S: Nampa, Idaho 83686 S: USA +N: Dirk J. ...

Implements the basic life cycles of a 'struct wimax_dev', some common generic netlink functionality for marshalling calls to user space, and the device state machine. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- net/wimax/stack.c | 627 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 627 insertions(+), 0 deletions(-) create mode 100644 net/wimax/stack.c diff --git a/net/wimax/stack.c b/net/wimax/stack.c new file mode 100644 index ...

Provides wimax_reset() for the kernel to reset a wimax device as needed. Exports wimax_reset() over generic netlink to user space. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- net/wimax/op-reset.c | 129 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 129 insertions(+), 0 deletions(-) create mode 100644 net/wimax/op-reset.c diff --git a/net/wimax/op-reset.c b/net/wimax/op-reset.c new file mode 100644 index 0000000..e733267 --- /dev/null +++ ...

Hi All This patchset (or the linux-wimax GIT tree at git.kernel.org) merges the WiMAX subsystem and driver for the Intel 2400m Wireless WiMAX connection to the tree. We'd like to get it in for the 2.6.29 merge window. [read on for changelog since previous submit] [Note linux-wimax will have netdev as upstream, but there is a dependency for patches in gregkh's patches tree that forbid submitting against netdev for now -- so the base for this is said tree as of 11/19. See *2] WiMAX ...

In the same spirit as debugfs_create_*(), introduce helpers for exporting size_t values over debugfs. The only trick done is that the format verifier is kept at %llu instead of %zu; otherwise type warnings would pop up: format ‘%zu’ expects type ‘size_t’, but argument 2 has type ‘long long unsigned int’ There is no real way to fix this one--however, we can consider %llu and %zu to be compatible if we consider that we are using the same for validating in ...

Implements the firmware loader (using the bus-specific driver's backends for the actual upload). The most critical thing in here is the piece that puts the device in boot-mode from any other (undetermined) state, otherwise, it is just pushing the bytes from the firmware file to the device. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- drivers/net/wimax/i2400m/fw.c | 1095 +++++++++++++++++++++++++++++++++++++++++ 1 files changed, 1095 insertions(+), 0 deletions(-) create ...

This implements the backends for the generic driver (i2400m) to be able to load firmware to the USB device. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- drivers/net/wimax/i2400m/usb-fw.c | 340 +++++++++++++++++++++++++++++++++++++ 1 files changed, 340 insertions(+), 0 deletions(-) create mode 100644 drivers/net/wimax/i2400m/usb-fw.c diff --git a/drivers/net/wimax/i2400m/usb-fw.c b/drivers/net/wimax/i2400m/usb-fw.c new file mode 100644 index 0000000..5ad287c --- ...

This is a collection of functions used to control the device (plus a few helpers). There are utilities for handling TLV buffers, hooks on the device's reports to act on device changes of state [i2400m_report_hook()], on acks to commands [i2400m_msg_ack_hook()], a helper for sending commands to the device and blocking until a reply arrives [i2400m_msg_to_dev()], a few high level commands for manipulating the device state, powersving mode and configuration plus the routines to setup the device ...

Implements the generic probe and disconnect functions, plus WiMAX stack backends for device reset and message passing. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- drivers/net/wimax/i2400m/driver.c | 736 +++++++++++++++++++++++++++++++++++++ 1 files changed, 736 insertions(+), 0 deletions(-) create mode 100644 drivers/net/wimax/i2400m/driver.c diff --git a/drivers/net/wimax/i2400m/driver.c b/drivers/net/wimax/i2400m/driver.c new file mode 100644 index ...

Low overhead method to map generic netlink family IDs to the WiMAX device attached to them that optimizes for the case where most systems have a single WiMAX device, or at most, a very low number of WiMAX adaptors. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- net/wimax/id-table.c | 140 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 140 insertions(+), 0 deletions(-) create mode 100644 net/wimax/id-table.c diff --git a/net/wimax/id-table.c ...

These two files are what user space can use to establish communication with the WiMAX kernel API and to speak the Intel 2400m Wireless WiMAX connection's control protocol. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> Cc: David Woodhouse <dwmw2@infradead.org> --- include/linux/Kbuild | 2 ++ include/linux/wimax/Kbuild | 1 + 2 files changed, 3 insertions(+), 0 deletions(-) create mode 100644 include/linux/wimax/Kbuild diff --git a/include/linux/Kbuild ...

When the device has anything for the host (namely when there is data ready to be read or when it resets), it sends a notification to the host; this is the code that receives and deals with them, passing reads to i2400m_rx() or handling resets with i2400m_dev_reset_handle(). Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- drivers/net/wimax/i2400m/usb-notif.c | 263 ++++++++++++++++++++++++++++++++++ 1 files changed, 263 insertions(+), 0 deletions(-) create mode 100644 ...

Expose knobs to control the stack's debug output. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- net/wimax/debugfs.c | 88 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 88 insertions(+), 0 deletions(-) create mode 100644 net/wimax/debugfs.c diff --git a/net/wimax/debugfs.c b/net/wimax/debugfs.c new file mode 100644 index 0000000..bb6ef52 --- /dev/null +++ b/net/wimax/debugfs.c @@ -0,0 +1,88 @@ +/* + * Linux WiMAX + * Debugfs support + * + ...

This is a simple framework for tracking the amount of soft-errors in time, so that if they go over a certain threshold they can be considered hard errors and recovery started (instead of just retrying). We use this in the USB driver -- some of the USB errors are considered soft and retried. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- drivers/net/wimax/i2400m/edc.h | 90 ++++++++++++++++++++++++++++++++++++++++ 1 files changed, 90 insertions(+), 0 deletions(-) create ...

Implements the backend so that the generic driver can send data to the USB device. Implemented with a kthread sitting in a never-ending loop that when kicked by the generic driver will pull data from the TX FIFO and send it to the device until it drains it. Then it goes back sleep, waiting for another kick. This is a thread for similar reasons as the case of USB reading. We need to be able to use the USB autopm management functions, which are blocking. As well, it is dedicated to a single task, ...

Handling of data coming from the i2400m device (IP packets, control and diagnostics). This parses the received read transaction from the device, breaks it in chunks and passes it to the corresponding subsystems (network and control). Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> --- drivers/net/wimax/i2400m/rx.c | 536 +++++++++++++++++++++++++++++++++++++++++ 1 files changed, 536 insertions(+), 0 deletions(-) create mode 100644 drivers/net/wimax/i2400m/rx.c diff --git ...

From: Alan Cox <alan@redhat.com> Remove all the extra casting while we are cleaning up Signed-off-by: Alan Cox <alan@redhat.com> --- drivers/net/wan/x25_asy.c | 10 +++++----- drivers/net/wireless/strip.c | 10 +++++----- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/drivers/net/wan/x25_asy.c b/drivers/net/wan/x25_asy.c index e188699..762fb13 100644 --- a/drivers/net/wan/x25_asy.c +++ b/drivers/net/wan/x25_asy.c @@ -258,7 +258,7 @@ static void ...

From: Alan Cox <alan@redhat.com> We have various drivers that poke around directly and we need to clean this up before it causes problems. Signed-off-by: Alan Cox <alan@redhat.com> --- drivers/net/irda/irtty-sir.c | 7 +++---- drivers/net/slip.c | 11 +++++------ drivers/net/wan/x25_asy.c | 8 ++++---- drivers/net/wireless/strip.c | 8 +++----- 4 files changed, 15 insertions(+), 19 deletions(-) diff --git a/drivers/net/irda/irtty-sir.c ...

Dave, Here is another big round of updates intended for 2.6.29 -- mostly drivers stuff this time around. Please let me know if there are problems! Thanks, John --- Individual patches are available here: http://www.kernel.org/pub/linux/kernel/people/linville/wireless-next-2.6/ --- The following changes since commit e061b165c7f4ec5e2e160d990b49011b5b6e5c6a: Martin Willi (1): xfrm: Accept ESP packets regardless of UDP encapsulation mode are available in the git ...

Hello, Attached is a patch which implements the Micrel KS8695 SoC's Ethernet interfaces. The driver is only of use on the KS8695. Regards, Daniel. -- Daniel Silverstone http://www.simtec.co.uk/ PGP mail accepted and encouraged. Key Id: 2BC8 4016 2068 7895

Simply replace netdev->priv with netdev_priv(). Compile test only. Signed-off-by: Wang Chen <wangchen@cn.fujitsu.com> --- drivers/staging/slicoss/slicoss.c | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index 8fa9490..0039036 100644 --- a/drivers/staging/slicoss/slicoss.c +++ b/drivers/staging/slicoss/slicoss.c @@ -765,8 +765,7 @@ static int slic_ioctl(struct net_device *dev, struct ...

In this driver, netdev's private data is wlandevice_t. And the wlandev(type of wlandevice_t) is exist before netdev be allocated. So use netdev->ml_priv to point to the private data. I am not sure whether I should consider the kernel version older than 2.3.38. Because in those kernels, netdevice_t is "structure dev" instead of "structure net_device" and of course "dev->ml_priv" will cause compile error. But before my patch, in function wlan_setup(), there is a ether_setup(net_device) which ...

Applied, thanks. --

Fix incorrect use of loose in spider_net.c It should be 'lose', not 'loose'. Signed-off-by: Nick Andrew <nick@nick-andrew.net> --- drivers/net/spider_net.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/net/spider_net.c b/drivers/net/spider_net.c index 07599b4..325fbc9 100644 --- a/drivers/net/spider_net.c +++ b/drivers/net/spider_net.c @@ -789,7 +789,7 @@ spider_net_set_low_watermark(struct spider_net_card *card) * spider_net_release_tx_chain ...

From: Pekka Savola <pekkas@netcore.fi> From what I've read, ipv4 mapped addresses are full of all kinds of tricky cases and issues. And, given that, using ipv4 mapped address for ipv4 multicast is just asking for trouble in my opinion. --

Hello. I think similar issue(s) have been pointed out several times. IPv4-mapped addresses are not portable, unfortunately, anyway, and people should use native interface, especially for multicasts. BTW, do you know what kind of socket option do they use for setting/getting ttl etc? If we fully support "IPv4-Mapped" function, we should transparently I don't think this could not be an answer. --yoshfuji --

build-r6999.out:/local/linsrc/linux-next-20081204/net/netlabel/netlabel_domainhash.c:527: error: implicit declaration of function 'netlbl_af6list_foreach_rcu' build-r6999.out:/local/linsrc/linux-next-20081204/net/netlabel/netlabel_domainhash.c:528: error: expected ';' before 'goto' 7005 same build-r7002.out:/local/linsrc/linux-next-20081204/net/bluetooth/rfcomm/sock.c:795: error: 'sk' undeclared (first use in this ...

Your patch is corrupted, tabs characters have been turned into spaces by your email client. Please fix this up and make a new submission your patch. Thank you. --

applied to merge. Guys, can you put a [for 2.6.28] or something if a patch is intended for .28.. this way I hopefully pay a bit more attention. - k --

A mac-vlan can't really be PROMISC either since it only receives BCAST frames and packets destined for it's own MAC, so I can't see how it could work in a bridge.... user-space brctl could check for the driver string returned by ethtool API to check if no one wants any additional cruft in the kernel... You might try using a pair of VETH interfaces to bridge between your host and virtual host. Thanks, Ben -- Ben Greear <greearb@candelatech.com> Candela Technologies Inc ...

I suspect we need the following un-tested diff to map all of these proc/ filesystem types to "proc" for the policy lookup at filesystem mount time. diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c index 9155fa9..3c3ceb7 100644 --- a/security/selinux/hooks.c +++ b/security/selinux/hooks.c @@ -703,7 +703,7 @@ static int selinux_set_mnt_opts(struct super_block *sb, sbsec->proc = 1; /* Determine the labeling behavior to use for this filesystem type. */ - rc = ...

The thing is I believe I changed the internal filesystem test to strncmp(fstype, "proc", 4); Which should match both proc and proc/net And likewise I thought I provided the same name by for the magic label Yes. Was the piece I missed in the LSM rules loaded from user space? Eric --

Hi The queues are different for each NPE, aren' t they? I will check for the 64-queue support patch (thanks Karl). However, if I am not sure they are required. I mean... - HSS0 uses queues 12-22. - HSS1 uses queues 0-10. - That leaves us 10 queues free, doesn't it? Couldn't we use queue 11 for eth txreadyq, 23-26 for HSS0 txreadyq, 27-30 for HSS1 txreadyq and I think your code is quite useful and structured, so it will be very interesting to have it mainstream. I was trying to ...

Hi ¿The message is the HSS_CONFIG_CORE_CR containing the I understand this, but I do not know exactly how to use it. I mean... - I have seen that more queues are added for tx and rxfree, but not rx or txdone... Are they not require? - Must we use different txreadyq for each hdlc? - The values you have chosen for txreadyq are 2 and 19. Does it not conflict with HSS0_PKT_RXFREE1_QUEUE and HSS1_PKT_RXFREE1_QUEUE. Shouldn't we use 23 and 24 (for example)? - I am not sure which documentation did ...

"ASPM: Could not configure common clock\n"? ASPM should still work, though with higher latency. It probably also needs to revert the configuration changes. -- Matthew Garrett | mjg59@srcf.ucam.org --

Hi You are absolutely right with create_chan function... I read it badly. Miguel Ángel Álvarez --

From: Hermann Lauer <Hermann.Lauer@iwr.uni-heidelberg.de> Again, thanks for doing this work. We don't want to run this code on MDIO phys, so at least a test is needed to guard this new code. And this new code is just a copy of the PHY init sequence on PCS, so we should split that out into a helper function instead of duplicating it. Any time gem_reset() is invoked, the PCS is going to need to be reset like this, so let's do the advertisement reinit there. Does this version of the fix ...