> > ...
> > results in two events:
> > 1. IN_DELETE_SELF (mask=0x0400)
> > 2. IN_IGNORED (mask=0x8000)
> >
> > Any ideas?
>
> "/mnt" is not unmounted, stuff inside of it is.
>
> Watch, say, "/mnt/foo/bar" and when /dev/hda1 is unmounted, you will get
> an IN_UNMOUNT on the watch.
I tried th
This patch just gathers together all the struct flock definitions except
xtensa into asm-generic/fcntl.h.
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
include/asm-alpha/fcntl.h |8
include/asm-arm/fcntl.h |8
include/asm-arm26/fcntl.h |8
This makes sense now that we have asm-powerpc.
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
include/asm-powerpc/fcntl.h | 11 +++
include/asm-ppc/fcntl.h | 11 ---
include/asm-ppc64/fcntl.h |1 -
3 files changed, 11 insertions(+), 12 deletions(-)
create
This patch puts the most popular of each fcntl operation/flag into
asm-generic/fcntl.h and cleans up the arch files.
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
include/asm-arm/fcntl.h | 21 -
include/asm-arm26/fcntl.h | 21 -
include
This patch gathers all the struct flock64 definitions (and the
operations), puts them under !CONFIG_64BIT and cleans up the arch files.
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
include/asm-arm/fcntl.h | 12
include/asm-arm26/fcntl.h | 12
includ
This set of patches creates asm-generic/fcntl.h and consolidates as much
as possible from the asm-*/fcntl.h files into it. Last time I posted
this, it caused no discussion at all - therefore people must agree with
it. :-)
I have built this for ppc64 (various configs) and ppc.
The patch split up
This patch just gathers all the identical bits of the asm-*/fcntl.h
files into asm-generic/fcntl.h.
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
include/asm-alpha/fcntl.h | 25 +
include/asm-arm/fcntl.h | 27 ++-
include/asm-ar
These two files are basically identical, so make one just include the
other (protecting the 32-bit-only parts with __powerpc64__). Also remove
some completely unused defines.
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
include/asm-ppc/fcntl.h | 12 +++-
include/asm-ppc64/fcn
This patch puts the most popular of each open flag into
asm-generic/fcntl.h and cleans up the arch files.
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
include/asm-alpha/fcntl.h |2 --
include/asm-arm/fcntl.h | 12 --
include/asm-arm26/fcntl.h | 10
inc
On Tue, Aug 30, 2005 at 08:06:21PM +, Holger Kiehl wrote:
> >>How does one determine the PCI-X bus speed?
> >
> >Usually only the card (in your case the Symbios SCSI controller) can
> >tell. If it does, it'll be most likely in 'dmesg'.
> >
> There is nothing in dmesg:
>
>Fusion MPT base dr
On 8/31/05, raja <[EMAIL PROTECTED]> wrote:
> Hi,
> Would you please suggest me the good books for linux device
> drivers.Because I want to implement linux Char,Block,PCI,USB
> Drivers.Would you please suggest the good books pertaining to coding please
http://lwn.net/Kernel/LDD3/ - excellent b
* Daniel Walker <[EMAIL PROTECTED]> wrote:
> Ingo,
> This patch adds a vermagic hook so PREEMPT_RT modules can be
> distinguished from PREEMPT_DESKTOP modules.
vermagic is very crude and there are zillions of other details and
.config flags that might make a module incompatible. You can u
On Wed, Aug 31 2005, Vojtech Pavlik wrote:
> On Tue, Aug 30, 2005 at 08:06:21PM +, Holger Kiehl wrote:
> > >>How does one determine the PCI-X bus speed?
> > >
> > >Usually only the card (in your case the Symbios SCSI controller) can
> > >tell. If it does, it'll be most likely in 'dmesg'.
> > >
On Tue, Aug 30 2005, [EMAIL PROTECTED] wrote:
>
> I ran across a memory leak related to the cfq scheduler. The cfq
> init function increments the refcnt of the associated request_queue.
> This refcount gets decremented in cfq's exit function. Since blk_cleanup_queue
> only calls the elevator exit
On Wed, Aug 31 2005, Nathan Scott wrote:
> Hi Jens,
>
> On Wed, Aug 24, 2005 at 11:28:39AM +0200, Jens Axboe wrote:
> > Patch attached is against 2.6.13-rc6-mm2. Still a good idea to apply the
> > relayfs read update from the previous mail [*] as well.
>
> There's a small memory leak there on one
On Wed, Aug 31 2005, Nathan Scott wrote:
> Hi Jens,
>
> On Wed, Aug 24, 2005 at 11:28:39AM +0200, Jens Axboe wrote:
> > Ok, updated version.
>
> One thing I found a bit awkward was the way its putting all inodes
> in the root of the relayfs namespace, with the cpuid tacked on the
> end of the bde
* Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> Do a "tar cvf usr.tar /usr" just to read/write a lot to disk (this
> within the same SATA disk). Watch memory being used in a system
> monitor applet up to 100%. After a while, hard to say how long (maybe
> 10/15 minutes?) the system eventu
* Alistair John Strachan <[EMAIL PROTECTED]> [050830 18:57]:
> On Tuesday 30 August 2005 13:31, Tony Lindgren wrote:
> [snip]
> > >
> > > Same issue, it's waiting on dynticks before being reworked.
> >
> > Also one more minor issue; Dyntick can cause slow boots with dyntick
> > enabled from boot be
Ulrich Drepper wrote:
On 8/29/05, Alan Cox <[EMAIL PROTECTED]> wrote:
Fixing it might be useful in some obscure cases anyway - POSIX threads
might benefit from it too, providing the functionality of changing all
thread uids at once isnt triggered for sensible threaded app behaviour.
I
Hi, I am trying to do a small amount of work on the wcfxo device driver
(or an fxo card), which is part of zapatel, which is used by asterisk,
the linux open source PBX (hence cross post).
question 1: Are PCI Master Aborts delivered to all subsystems, if they
are, do I need to "fix" ALL the dr
* Jeff Garzik:
> There is still the open question of whether this is legal enough to
> include in the kernel :(
Are you referring to FTC issues, or potential copyright/trade secret
issues?
The FTC issues are shared by many (most?) wireless drivers. The
copyright/trade secret issues might be wo
--- David Brownell <[EMAIL PROTECTED]> wrote:
> The last couple times SPI frameworks came up here,
> some of the feedback
> included "make it use the driver model properly;
> don't be like I2C".
>
> In hopes that it'll be useful, here's a small SPI
> core with driver model
> support driven from
Alan Cox wrote:
On Llu, 2005-08-29 at 11:54 +0800, qiyong wrote:
We can ignore it safely. sys_promote is a different approach from
selinux. sys_promote is to let sysadmin manually manipulate a running
process,
You can ignore the patch easily enough. Ignoring the locking doesn't
wor
Chris Wright ([EMAIL PROTECTED]) wrote:
> * David Härdeman ([EMAIL PROTECTED]) wrote:
> > I'm currently playing around with the security/root_plug.c LSM module
> you'll have better luck on the lsm list
Thanks for the pointer
> > 1) What's the recommended way of telling that someone is logging in
On Mon, Aug 29 2005, Erik Mouw wrote:
> There are four prerequisites for direct IO:
> - the file needs to be opened with O_DIRECT
> - the buffer needs to be page aligned (hint: use getpagesize() instead
> of assuming that a page is 4k
> - reads and writes need to happen *in* multiples of the soft
Florian Weimer <[EMAIL PROTECTED]> wrote:
-> The FTC issues are shared by many (most?) wireless drivers. The
-> copyright/trade secret issues might be worked around by basing the
-> work on the OpenBSD version of that driver (and someone is actually
-> working on that).
the problem with openbsd
i have no freaking idea of coding. but going throught this "Discuss
issues related to the xorg tree" talk, made me feel and say "mommy
(coder), daddy (admin), please dont fight you tearing
us(users) apart."
glad its worked out.. all i hope is we(users) , now , get some nice
fast xorg :D.
Sorry, I send out wrong version. I attached the latest patch to 2.6.13.
OGAWA Hirofumi wrote:
"Machida, Hiroyuki" <[EMAIL PROTECTED]> writes:
Here is a revised version of dirent scan patch, mentioned at
following E-mail.
This patch addresses performance damages on "ls | xargs xxx" and
reve
* Mateusz Berezecki:
> Florian Weimer <[EMAIL PROTECTED]> wrote:
> -> The FTC issues are shared by many (most?) wireless drivers. The
> -> copyright/trade secret issues might be worked around by basing the
> -> work on the OpenBSD version of that driver (and someone is actually
> -> working on th
On Wed, 2005-08-31 at 10:44 +0300, Tony Lindgren wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> [050830 18:57]:
> > On Tuesday 30 August 2005 13:31, Tony Lindgren wrote:
> > [snip]
> > > >
> > > > Same issue, it's waiting on dynticks before being reworked.
> > >
> > > Also one more minor iss
On Wednesday 31 August 2005 11:16, Mateusz Berezecki wrote:
> Florian Weimer <[EMAIL PROTECTED]> wrote:
> -> The FTC issues are shared by many (most?) wireless drivers. The
> -> copyright/trade secret issues might be worked around by basing the
> -> work on the OpenBSD version of that driver (and
As per the feature-removal.txt file, I will be removing the following
functions shortly:
* register_serial
* unregister_serial
* uart_register_port
* uart_unregister_port
However, there are still some drivers which use these functions:
drivers/char/mwave/mwavedd.c
Stephen Hemminger wrote:
You have a version of the Marvell Yukon that was affected
by a fix in 2.6.13.
skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9
Both the skge and sk98lin driver were fixed to check for this.
Without the fix, the chip will be in the wrong power mode.
The version
Hi,
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
> +inline
> +static int hint_allocate(struct inode *dir)
> +{
> + loff_t *hints;
> + int err = 0;
> +
> + if (!MSDOS_I(dir)->scan_hints) {
> + hints = kcalloc(FAT_SCAN_NWAY, sizeof(loff_t), GFP_KERNEL);
>
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
> +inline
> +static int hint_index_body(const unsigned char *name, int name_len, int
> check_null)
> +{
> + int i;
> + int val = 0;
> + unsigned char *p = (unsigned char *) name;
> + int id = current->pid;
> +
> +
On Mon, Aug 29, 2005 at 09:55:04PM +0400, Grigory Tolstolytkin wrote:
> I'm working on power management support for a particular ARM based board
> and I've got a question:
> I want to add a board specific power management for standard uart driver
> (serial8250). For this purpose there is a specia
On Thu, Aug 25, 2005 at 01:20:45PM +0100, Rahul Tank wrote:
> I am a newbee tryinging for serial port
> multiplexing. Currently my driver supports for one
> port
> (/dev/ttyS0). However i want to use the same physical
> port for 2 virtual ports.I am NOT sending two type of
> data simultaneously
Hi,
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
>
> Sorry, I send out wrong version. I attached the latest patch to 2.6.13.
>
> OGAWA Hirofumi wrote:
> > "Machida, Hiroyuki" <[EMAIL PROTECTED]> writes:
> >
> >
> >>Here is a revised version of dirent scan patch, mentioned at
> >>fol
On Wed, 2005-08-31 11:10:48 +0100, Russell King <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 25, 2005 at 01:20:45PM +0100, Rahul Tank wrote:
> > I am a newbee tryinging for serial port
> > multiplexing. Currently my driver supports for one
> > port
> > (/dev/ttyS0). However i want to use the same p
On Wed, Aug 31, 2005 at 12:16:10PM +0200, Jan-Benedict Glaw wrote:
> On Wed, 2005-08-31 11:10:48 +0100, Russell King <[EMAIL PROTECTED]> wrote:
> > On Thu, Aug 25, 2005 at 01:20:45PM +0100, Rahul Tank wrote:
> > > I am a newbee tryinging for serial port
> > > multiplexing. Currently my driver s
Florian Weimer <[EMAIL PROTECTED]> wrote:
-> > the problem with openbsd version of the hal is that it is - sorry to
-> > say that - fundamentally broken, at least it was last time I was
-> > checking.
->
-> It's better than nothing, that is, it worked for us when we gave it a
-> try. And it se
Denis Vlasenko <[EMAIL PROTECTED]> wrote:
-> What it can do? In particular, can it:
-> * send packets with arbitrary contents? In particular, packets
-> shorter than 3-address 802.11 header? packets with WEP bit set?
-> Does it allow to do WEP encoding by host instead of hal?
-> Any weird lim
* Arjan van de Ven <[EMAIL PROTECTED]> [050831 11:40]:
> On Wed, 2005-08-31 at 10:44 +0300, Tony Lindgren wrote:
> > * Alistair John Strachan <[EMAIL PROTECTED]> [050830 18:57]:
> > > On Tuesday 30 August 2005 13:31, Tony Lindgren wrote:
> > > [snip]
> > > > >
> > > > > Same issue, it's waiting on
Brett Russ napsal(a):
This is the first public release of my libata compatible low level driver for
the Marvell SATA family. Currently it successfully runs in PIO mode on a 6081
chip. EDMA support is in the works and should be done shortly. Review,
testing (especially on other flavors of Marv
On Wed, Aug 31, 2005 at 01:34:03PM +0300, Tony Lindgren wrote:
> Well it seems like the next_timer_interrupt is something like 400
> jiffies away and RCU code waits for completion for example in the
> network code.
I had a patch to fix the problem of "RCU grace period extended
because of sleeping
Hi Grigory,
it's unclear from your letter where you take pnx4008_uart_pm from. Can
you please elaborate?
What I would think of if I were you is adding a field 'pm' to struct
plat_serial8250_port which is filled in in the architecture-specific
part and setting up->pm accrodingly.
I'll send a
> > ehh
> > why does it cause slow boots?
> > if that kind of behavior changes... isn't that a sign there is a
> > fundamental bug still ?
>
> Well it seems like the next_timer_interrupt is something like 400
> jiffies away and RCU code waits for completion for example in the
> network code.
th
Greetings,
please find the patch that allows passing the pointer to custom power
management routine (via platform_device) to 8250 serial driver.
Please note that the interface to the outer world (i. e. exported
functions) remained the same.
Best regards,
Vitaly
Currently 8250 serial driver d
On Wed, Aug 31, 2005 at 10:07:45AM +0200, Jens Axboe wrote:
> On Mon, Aug 29 2005, Erik Mouw wrote:
> > There are four prerequisites for direct IO:
> > - the file needs to be opened with O_DIRECT
> > - the buffer needs to be page aligned (hint: use getpagesize() instead
> > of assuming that a pag
On Wed, Aug 31 2005, Erik Mouw wrote:
> On Wed, Aug 31, 2005 at 10:07:45AM +0200, Jens Axboe wrote:
> > On Mon, Aug 29 2005, Erik Mouw wrote:
> > > There are four prerequisites for direct IO:
> > > - the file needs to be opened with O_DIRECT
> > > - the buffer needs to be page aligned (hint: use ge
On Wed, Aug 31, 2005 at 01:03:05PM +0200, Arjan van de Ven wrote:
> that sounds like a fundamental issue that really needs to be fixed
> first!
It should be fixed by the patch here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=111556608901657&w=2
Tony,
I don't see any slow bootups on x8
Sorry for format. Attached is the better one :)
Vitaly Wool wrote:
Greetings,
please find the patch that allows passing the pointer to custom power
management routine (via platform_device) to 8250 serial driver.
Please note that the interface to the outer world (i. e. exported
functions) rema
On Wed, Aug 31, 2005 at 04:47:05PM +0530, Srivatsa Vaddagiri wrote:
> On Wed, Aug 31, 2005 at 01:03:05PM +0200, Arjan van de Ven wrote:
> > that sounds like a fundamental issue that really needs to be fixed
> > first!
>
> It should be fixed by the patch here:
> http://marc.theaimsgroup.com/?l=linu
On Wed, Aug 31, 2005 at 03:10:09PM +0400, Vitaly Wool wrote:
> please find the patch that allows passing the pointer to custom power
> management routine (via platform_device) to 8250 serial driver.
> Please note that the interface to the outer world (i. e. exported
> functions) remained the same
>
> The two different uses of the superblock lock are really quite
> different; I don't see any particular problem with using two different
> locks for the two different things. Mount and the namespace code are
> not locking the same thing --- the fact that the resize code uses the
> superblock l
Yes, that's also something I was thinking of, but I wasn't sure enough
in this radical change :)
Anyway, I do agree that this way looks better than the current one.
So, if you don't object against other changes (say, the suggested
approach to set uart->pm), I can proceed with the changes you sug
On Tue, 30 Aug 2005, Dave McCracken wrote:
>
> This patch implements page table sharing for all shared memory regions that
> span an entire page table page. It supports sharing at multiple page
> levels, depending on the architecture.
>
> Performance testing has shown no degradation with this pa
Jiri Slaby wrote:
+static struct pci_device_id mv_pci_tbl[] = {
+{PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 0x5040), 0, 0, chip_504x},
+{PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 0x5041), 0, 0, chip_504x},
+{PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 0x5080), 0, 0, chip_508x},
+{PCI_DEVICE(PCI_VENDOR_ID_M
On Wed, 2005-08-31 at 12:44 +0100, Hugh Dickins wrote:
> I was going to say, doesn't randomize_va_space take away the rest of
> the point? But no, it appears "randomize_va_space", as it currently
> appears in mainline anyway, is somewhat an exaggeration: it just shifts
> the stack a little, with n
On Wed, 31 Aug 2005, Jens Axboe wrote:
On Wed, Aug 31 2005, Vojtech Pavlik wrote:
On Tue, Aug 30, 2005 at 08:06:21PM +, Holger Kiehl wrote:
How does one determine the PCI-X bus speed?
Usually only the card (in your case the Symbios SCSI controller) can
tell. If it does, it'll be most lik
Nathan Becker wrote:
I would be happy to post my exact C source that I use to do the
benchmark, but I wanted to get some feedback first in case I'm just
doing something stupid. Also, since I'm not subscribed to this list,
please cc me directly regarding this topic.
Hi Nathan,
Cache issu
On Tue, Aug 30, 2005 at 10:45:54PM +0200, Jesper Juhl wrote:
>
> I've posted similar patches in the past, but was asked to first until the
> short-circuit patch moved from -mm to mainline - and since it is now
> firmly there in 2.6.13 I assume there's no problem there anymore.
> I was also asked
Ingo Molnar <[EMAIL PROTECTED]> writes:
> - if everything fails and automatic latency tracing does not show
> anything out of ordinary, then you could try to do "user-triggered
> tracing" of jackd's critical path. This is more laborous to do, but
> should pinpoint the latency reason in a p
On Wed, Aug 31 2005, Holger Kiehl wrote:
> >>>Ok, I did run the following dd command in different combinations:
> >>>
> >>> dd if=/dev/zero of=/dev/sd?1 bs=4k count=500
> >>
> >>I think a bs of 4k is way too small and will cause huge CPU overhead.
> >>Can you try with something like 4M? Also,
* Nick Matteo <[EMAIL PROTECTED]> wrote:
> The other day I was running a grep on a big directory tree and got a
> "Argument list too long" error. Since I'd like to have this work
> without messing with find and xargs each time, I went into
> include/linux/binfmts.h and changed
>
> #define MA
Hi,
-rc6-mm2 breaks USB unplug for me. Happens with every USB device,
gcc-3.3.5 and gcc-3.4.4 as well as preempt and non-preempt and is 100%
reproducible.
-rc6-mm1 seems fine.
Reverting the following part of
driver-core-fix-bus_rescan_devices-race.patch
fixes this for me:
diff -puN drivers/base/
On Wed, Aug 24, 2005 Philipp Matthias Hahn wrote:
> Integrate saa7146_i2c adapter into device model:
> Moves entries from /sys/device/platform to /sys/device/pci*.
>
> Signed-off-by: Philipp Hahn <[EMAIL PROTECTED]>
I added this patch to linuxtv.org CVS.
Thanks,
Johannes
> --- linux/drivers/me
On 8/31/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi everyone:
>
> I am implemnting one ioctl() in one character device.
>
> That need know instruction pointer of user space. I am on i386
> platform.
> I can sure I am in process context. and enter kernel by system call way.
>
>
On Wed, Aug 31, 2005 at 02:11:44PM +0200, Ingo Molnar wrote:
> > I recompiled and installed the kernel, but there's no change (getconf
> > ARG_MAX still gives 131072.) What am I missing?
>
> MAX_ARG_PAGES should work just fine. I think the 'getconf ARG_MAX'
> output is hardcoded. (because the k
Holger Kiehl wrote:
3236497 total 1.4547
2507913 default_idle 52248.1875
158752 shrink_zone 43.3275
121584 copy_user_generic_c 3199.5789
34271 __wake_up_bit
On Sun, Aug 28, 2005 Al Viro wrote:
> Signed-off-by: Al Viro <[EMAIL PROTECTED]>
I added this patch to linuxtv.org CVS.
Thanks,
Johannes
> diff -urN RC13-rc7-base/drivers/media/dvb/frontends/tda80xx.c
> current/drivers/media/dvb/frontends/tda80xx.c
> --- RC13-rc7-base/drivers/media/dvb/frontend
On Mer, 2005-08-31 at 10:33 +0100, Russell King wrote:
> Unfortunately, it appears that some of these drivers do not contain
> email addresses for their maintainers, neither are they listed in
> the MAINTAINERS file. (mwavedd and serial_txx9).
I'll have a quick look at mwave. If I remember rightl
Phy Prabab wrote:
Hello all,
I am seeing something odd w/sockets. I have an app
that opens and closes network sockets. When the app
terminates it releases all fd (sockets) and exists,
yet running netstat after the app terminates still
shows the sockets as open! Am I doing something wrong
or i
Something like below, which has the advantange that there is still only
one implementation of the function
True, that´s a great advantage.
and if it's still slower, we really need to check the compiler
Please have a look at the following patch. It takes your idea of
inlining but moves
t
Hi all!
Just for the logs, the getprlimit/setprlimit system call for the
2.6.13 plus a man page in case sombody cares.
Again my request to those who reviewed my first try, maybe you could
have a look at this if locking is better now, I do not break SELinux
anymore etc. so I can shift to the 64 Bi
The patch for the getprlimit() syscall:
Signed-off-by: Wieland Gmeiner <[EMAIL PROTECTED]>
---
arch/i386/kernel/syscall_table.S |1
include/asm-i386/unistd.h|3 -
include/linux/security.h | 25 ++-
kernel/sys.c | 85 +++
The patch for the setprlimit() syscall:
Signed-off-by: Wieland Gmeiner <[EMAIL PROTECTED]>
---
arch/i386/kernel/syscall_table.S |1
include/asm-i386/unistd.h|3 -
kernel/sys.c | 114 ---
security/selinux/hooks.c
On Wed, Aug 31, 2005 at 02:00:24PM +0100, Alan Cox wrote:
> On Mer, 2005-08-31 at 10:33 +0100, Russell King wrote:
> > Unfortunately, it appears that some of these drivers do not contain
> > email addresses for their maintainers, neither are they listed in
> > the MAINTAINERS file. (mwavedd and se
Hi,
Pekka Enberg wrote:
Hi,
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
+inline
+static int hint_allocate(struct inode *dir)
+{
+ loff_t *hints;
+ int err = 0;
+
+ if (!MSDOS_I(dir)->scan_hints) {
+ hints = kcalloc(FAT_SCAN_NWAY, sizeof(loff_t), GF
Hi,
Thank you checking code...
Pekka Enberg wrote:
Hi,
:
snip
This patch enables using hint information on scanning dir.
It achieves excellent performance with "ls -l" for over 1000 entries.
* fat-dirscan-with-hint_3.patch for linux 2.6.13
fs/fat/dir.c | 130
On Mer, 2005-08-31 at 01:19 +0200, Sven Ladegast wrote:
> On Wed, 31 Aug 2005, Alan Cox wrote:
>
> > "Register a box + optional PCI id list/CPU info"
> > Reply with a secured serial number
>
> Registering means to create an ID for the system? Something out of
> timestamp plus your PCI IDs and CP
On Mer, 2005-08-31 at 13:52 +0100, Russell King wrote:
> The key thing is that port.dev should be set appropriately and the
> relevant calls to serial8250_suspend_port/serial8250_resume_port
> be made (or port.dev should be NULL if no power management is
> expected - in which case it may be managed
Hi Andi, hi everyone,
The MP_valid_apicid() function [arch/i386/kernel/mpparse.c] checks
whether the APIC version field is >=20 in order to determine whether
the CPU supports 8-bit physical APIC ids.
Yes, it's broken. ... . Also it's only
a sanity check for broken BIOS, and in this case it cau
* Srivatsa Vaddagiri <[EMAIL PROTECTED]> [050831 14:20]:
> On Wed, Aug 31, 2005 at 04:47:05PM +0530, Srivatsa Vaddagiri wrote:
> > On Wed, Aug 31, 2005 at 01:03:05PM +0200, Arjan van de Ven wrote:
> > > that sounds like a fundamental issue that really needs to be fixed
> > > first!
> >
> > It shou
On Wed, 31 Aug 2005, Martin Wilck wrote:
> We are wondering why these masks are there in the subarch code at all. After
> all, whether or not 8-bit APIC IDs are supported depends mainly on the CPU
> type used. Why wouldn't it possible to have a "default" architecture with APIC
> IDs > 15, if the C
Pekka Enberg wrote:
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
+inline
+static int hint_index_body(const unsigned char *name, int name_len, int
check_null)
+{
+ int i;
+ int val = 0;
+ unsigned char *p = (unsigned char *) name;
+ int id = current->pid;
+
+
Hello,
Using aoe on a sparc64 system gives strange results:
sunny:/dev/etherd# echo >discover
sunny:/dev/etherd# mke2fs e0.0
mke2fs 1.37 (21-Mar-2005)
mke2fs: File too large while trying to determine filesystem size
sunny:/dev/etherd# blockdev --getsz e0.0
-4503599627370496
The log says:
Aug 31
Seems patches stored on ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots
are empty (only logs are correct):
$ lftp ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots
cd ok, cwd=/pub/linux/kernel/v2.6/snapshots
lftp ftp.kernel.org:/pub/linux/kernel/v2.6/snapshots> ls patch-2.6.13-git*
-rw-r
On 8/31/05, Eric Anholt <[EMAIL PROTECTED]> wrote:
> the X Render extension." No, EXA is a different acceleration
> architecture making different basic design decisions related to memory
> management and driver API.
I did start the EXA section off with this: "EXA replaces the existing
2D XAA driv
Jens Axboe wrote:
> On Tue, Aug 30 2005, [EMAIL PROTECTED] wrote:
>
>>I ran across a memory leak related to the cfq scheduler. The cfq
>>init function increments the refcnt of the associated request_queue.
>>This refcount gets decremented in cfq's exit function. Since blk_cleanup_queue
>>only call
On Wed, 31 Aug 2005, Arjan van de Ven wrote:
> On Wed, 2005-08-31 at 12:44 +0100, Hugh Dickins wrote:
> > I was going to say, doesn't randomize_va_space take away the rest of
> > the point? But no, it appears "randomize_va_space", as it currently
> > appears in mainline anyway, is somewhat an exag
On Wed, Aug 31 2005, Brian King wrote:
> Jens Axboe wrote:
> > On Tue, Aug 30 2005, [EMAIL PROTECTED] wrote:
> >
> >>I ran across a memory leak related to the cfq scheduler. The cfq
> >>init function increments the refcnt of the associated request_queue.
> >>This refcount gets decremented in cfq's
Hi,
the description of PCI_NAMES is conflicting with its default option (now
N/y/? instead of Y/n/?). Here is a small patch that should remove the
confusion in drivers/pci/Kconfig.
Regards,
Alexandre
Signed-off-by : Alexandre Buisse <[EMAIL PROTECTED]>
--- drivers/pci/Kconfig.old 2005-08-31
Hi,
On Wed, 2005-08-31 at 12:35, Glauber de Oliveira Costa wrote:
> At a first look, i thought about locking gdt-related data. But in a
> closer one, it seemed to me that we're in fact modifying a little bit
> more than that in the resize code. But all these modifications seem to
> be somehow rel
On Wed, 31 Aug 2005, Vojtech Pavlik wrote:
On Tue, Aug 30, 2005 at 08:06:21PM +, Holger Kiehl wrote:
How does one determine the PCI-X bus speed?
Usually only the card (in your case the Symbios SCSI controller) can
tell. If it does, it'll be most likely in 'dmesg'.
There is nothing in dm
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
> > Please consider moving this check to callers. Conditional allocation
> > makes this bit strange API-wise. Or alternatively, give
> > hint_allocate() a better name.
>
> How about hint_allocate_conditional() ?
hint_get() sounds better to
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
> How about this ?
>
> if (!MSDOS_I(dir)->scan_hints) {
> hints = kcalllo();
>
> down
> if (MSDOS_I(dir)->scan_hints) {
> up
> goto
On 8/31/05, Pekka Enberg <[EMAIL PROTECTED]> wrote:
> After finally understanding what you're doing, how about:
>
> static inline int hint_allocate(struct inode *dir)
> {
> loff_t *hints;
> int err = 0;
>
> if (!MSDOS_I(dir)->scan_hints)
Should read:
if (MSDOS_I(dir)->sc
Jens Axboe wrote:
> On Wed, Aug 31 2005, Brian King wrote:
>
>>Jens Axboe wrote:
>>
>>>On Tue, Aug 30 2005, [EMAIL PROTECTED] wrote:
>>>
>>>
I ran across a memory leak related to the cfq scheduler. The cfq
init function increments the refcnt of the associated request_queue.
This refcou
Greetings gentlemen,
please find the patch against 2.6.13 tree with Russel's proposal taken
into account.
This patch that allows passing the pointer to custom power management
routine (via platform_device) to 8250 serial driver.
Please note that the exported functions' API remained the same.
T
1 - 100 of 317 matches
Mail list logo
