- 08 Sep, 2004 40 commits
-
-
Andi Kleen authored
New version of the NETIF_F_LLTX for network devices patch. This allows network drivers to set the NETIF_F_LLTX flag and then do their own locking in start_queue_xmit. This lowers locking overhead in this critical path. The drivers can use try lock if they want and return -1 when the lock wasn't grabbed. In this case the packet will be requeued. For better compatibility this is only done for drivers with LLTX set, others don't give a special meaning to -1. Most of the modern drivers who have a lock around hard_start_xmit can just set this flag. It may be a good idea to convert the spin lock there to a try lock. The only thing that should be audited is that they do enough locking in the set_multicast_list function too, and not also rely on xmit_lock here. Now doesn't move any code around and does things with gotos instead. The loop printk is also still there even for NETIF_F_LLTX For drivers that don't set the new flag nothing changes. Signed-off-by:David S. Miller <davem@davemloft.net>
-
Hideaki Yoshifuji authored
Here's the optimization: if we know the remaining data exceeds the mtu, we do not need to fill up full of it. skb_prev: mtu +----------+--+-+ | | | | +----------+--+-+ ^ ^ skb_prev->len | maxfraglen appending data: +--------+ | | +--------+ ---------> length In this case, we know we need more fragment(s). So, let's fill up to maxfraglen (instead of mtu) to avoid needless copy in the next loop. Signed-off-by:Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org> Signed-off-by:
Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by:
-
Bart De Schuymer authored
Signed-off-by:
Bart De Schuymer <bdschuym@pandora.be> Signed-off-by:
-
David S. Miller authored
into nuts.davemloft.net:/disk1/BK/net-2.6
-
Andries E. Brouwer authored
Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Andries E. Brouwer authored
udf_filead_read() and udf_get_fileextent() are unused. Here they are put inside #if 0 .. #endif Signed-off-by:
-
Andries E. Brouwer authored
Signed-off-by:
-
Andries E. Brouwer authored
Signed-off-by:
-
Paul E. McKenney authored
Signed-off-by: <paulmck@us.ibm.com> Signed-off-by:
-
Olaf Hering authored
Alpha is AXP. hostname and domainname does not need redirection. Signed-off-by:
Olaf Hering <olh@suse.de> Signed-off-by:
-
Christoph Hellwig authored
The exports were for reiserfs in 2.4, but reiserfs doesn't need them anymore. Signed-off-by:
-
Christoph Hellwig authored
Doesn't even appear in Makefile and Kconfig anymore. Signed-off-by:
-
Andi Kleen authored
Current gcc 3.5 doesn't compile a x86-64 kernel, because it doesn't recognize the offsetof used in asm-offset.c to be constant. Use __builtin_offsetof for this instead. Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
-
Christoph Hellwig authored
the ibm_emac_mal.c one is in exported function, so useless, the other two are stale decrements. Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
-
Paolo \'Blaisorblade\' Giarrusso authored
Correct the failure path in start_io_thread(), to return the correct error code. Signed-off-by:
Paolo 'Blaisorblade' Giarrusso <blaisorblade_spam@yahoo.it> Signed-off-by:
-
Paolo \'Blaisorblade\' Giarrusso authored
Avoid forcing use of the no-op scheduler for UBD; this may uncover some bugs in the UBD driver, and in fact uml-ubd-no-empty-queue.patch is needed to make this sure. But as of now, no other bugs have been discovered, so this should be safe. Signed-off-by:
-
Paolo \'Blaisorblade\' Giarrusso authored
Avoid using, in the UBD driver, the elv_queue_empty function. It's for the block layer only; in fact, the Anticipatory Scheduler can return NULL with elv_next_request() even if the queue is not empty, because it waits for the process to send another request before seeking on the disk. In fact, if (with uml-ubd-any-elevator) we let UBD use any scheduler, elevator=as will make the UBD driver Oops, if we don't have this patch. Signed-off-by:
-
Andries E. Brouwer authored
Signed-off-by:
-
Andries E. Brouwer authored
The routine afs_rxvl_probe() is unused and could be removed. (I only put #if 0 around it.) Signed-off-by:
-
Andries E. Brouwer authored
Signed-off-by:
-
Ingo Molnar authored
Clean up the TSC-synchronization code: get rid of div64 and calm down the printks. Signed-off-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
Andries E. Brouwer authored
Signed-off-by:
-
Andries E. Brouwer authored
Signed-off-by:
-
Paul Fulghum authored
Uses msecs_to_jiffies() instead of the custom jiffies_from_ms(). Signed-off-by:
Nishanth Aravamudan <nacc@us.ibm.com> Signed-off-by:
-
Adrian Bunk authored
drivers/cdrom/cdu31a.c: In function `do_sony_cd_cmd': drivers/cdrom/cdu31a.c:962: parse error before `:' Signed-off-by:
Adrian Bunk <bunk@fs.tum.de> Signed-off-by:
-
Anton Blanchard authored
I noticed a large machine was doing about 400,000 context switches per second when oprofile was enabled. Upon closer inspection it looks like we were rearming the buffer sync timer without modifying the expire time. Now that we have schedule_delayed_work_on I believe we can remove the timer completely. Each cpu should be offset by 1 jiffy so they dont all fire at the same time. I bumped DEFAULT_TIMER_EXPIRE from 2 to 10 times a second to be sure we reap cpu buffers. With the following patch the same large machine gets about 4000 context switches per second. Signed-off-by:
Anton Blanchard <anton@samba.org> Signed-off-by:
-
Anton Blanchard authored
On error we can call __free_cpu_buffers with only some buffers allocated. I was getting a bunch of vfree warnings when I hit it, we should check before calling vfree. Signed-off-by:
-
Anton Blanchard authored
Replace open coded versions with for_each_cpu()/for_each_online_cpu(). Signed-off-by:
-
Adrian Bunk authored
drivers/char/riscom8.c:1178: macro `min_t' used with only 2 args Signed-off-by:
-
Badari Pulavarty authored
The problem here is, finished_one_bio() shouldn't call aio_complete() since no work has been done. I have a fix for this - can you verify this ? I am not really comfortable with this "tweaking". (I am not really sure about IO errors like EIO etc. - if they can lead to calling aio_complete() twice) Fix is to call aio_complete() ONLY if there is something to report. Note the we don't update dio->result with any error codes from get_user_pages(), they just passed as "ret" value from do_direct_IO(). Signed-off-by:
-
Thor Kooda authored
xtea_encrypt() should use XTEA_DELTA instead of TEA_DELTA. Signed-off-by:
Thor Kooda <tkooda-patch-kernel@devsec.org> Signed-off-by:
-
Dave Jones authored
This pointer is used prior to a test for NULL. But Bart says it can never be NULL. Signed-off-by:
Dave Jones <davej@redhat.com> Signed-off-by:
-
Dave Jones authored
Not that this driver compiles, but coverity picked up this nonsense. If the pci_alloc_consistent fails, we go boom. Amusingly, after the ==NULL check, is an identical memset. Signed-off-by:
-
Antonino Daplas authored
This adds module_init(xxxfb_init) in all drivers. For drivers with xxxfb_setup(), this patch also adds a 'xxxfb_setup(fb_get_options("xxxfb"))' prior to initialization. Signed-off-by:Antonino Daplas <adaplas@pol.net> Signed-off-by:
-
Antonino Daplas authored
This patch probably deserves discussion among developers. Currently, the framebuffer system is initialized in a roundabout manner. First, drivers/char/mem.c calls fbmem_init(). fbmem_init() will then iterate over an array of individual drivers' xxxfb_init(), then each driver registers its presence back to fbmem. During console_init(), drivers/char/vt.c will call fb_console_init(). fbcon will check for registered drivers, and if any are present, will call take_over_console() in drivers/char/vt.c. This patch changes the initialization sequence so it proceeds in this manner: Each driver has its own module_init(). Each driver calls register_framebuffer() in fbmem.c. fbmem.c will then notify fbcon of the driver registration. Upon notification, fbcon calls take_over_console() in vt.c. The following are the changes brought about by this patch: - Each subsystem (fbcon, fbmem, xxxfb) will have their own module_init. Thus, explicit calls to each subsystem's init functions are eliminated. - The struct fb_drivers array in fbmem.c can be removed. This slashes around 400 lines in fbmem.c - Parsing of kernel boot options were done by fbmem.c calling each driver's xxxfb_setup() function. Because this is not possible with this patch, drivers can choose to either: - have their own __setup() routine - call fb_get_options("xxxfb") and pass the return value to xxxfb_setup(). This is to maintain compatibility with the 'video=xxxfb:<options>' semantics. - Getting a framebuffer console will occur a bit late during the boot process since the initialization sequence will depend upon the link order. So, 'video/' is moved up in drivers/Makefile, shortly after 'pci/' - Because driver initialization will be dependent on the link order, hardware that depends on other subsystems (agpgart, usb, serial, etc) may choose to initialize after the subsystems they depend on. Signed-off-by: -
Antonino Daplas authored
- This fixes another regression from 2.4. If fbcon is compiled statically, and the framebuffer driver is compiled as a module, doing a 'modprobe xxxfb' does nothing to the console. This has generated numerous bug reports from users. With this patch, fbmem will notify fbcon upon driver registration allowing fbcon to take over the console. - This also fixes con2fbmap not working if fbcon is compiled as a module using the same mechanism as described above. Signed-off-by:
-
Antonino Daplas authored
- Fixed rivafb crashing in PPC. rivafb in PPC requires full, instead of partial, hardware initialization in rivafb_set_par(). - Added untested support for NV_ARCH_30 chipsets. - From Guido Guenther <agx@sigxcpu.org> here's another short patch fixing the cursor colors on big endian. - From Guido Guenther <agx@sigxcpu.org> trivial: strictmode is a MODULE_PARAM, even if CONFIG_MTRR is not set: Signed-off-by:Guido Guenther <agx@sigxcpu.org> Signed-off-by:
-
Antonino Daplas authored
This patch speeds up scrolling of tdfxfb by maximizing var->yres_virtual so tdfxfb uses SCROLL_PAN_MOVE instead of SCROLL_REDRAW. This is true whether CONFIG_FB_3DFX_ACCEL is set or not. This problem was reported by Paolo Ornati <ornati@fastwebnet.it> who also made substantial contributions to solve this problem. This patch also fixes compile errors when CONFIG_FB_3DFX_ACCEL is false. Signed-off-by:
-
