Dear all,
I have few basic queries regarding my partition implementation in my Sd
driver.
Sorry for asking such petty things here. But, somehow it's not working &
I am made to ask it here.
I am working on 2.6.10 kernel(x86 architecture).
I have a working SD driver for my multimedia controller.
On Wed, 2005-08-17 at 22:20 -0700, K Aruran wrote:
> Hai..
>
> I want to install 2.2.26 kernel on FC1 (2.4.22) for
> testing purpose of my modem..
>
> How can I install it...
you can't. Fedora Core 1 assumes a 2.4 kernel in MANY places, and an
NPTL capable kernel in somne.
-
To unsubscribe fro
Coywolf Qi Hunt a écrit :
On 8/18/05, Eric Dumazet <[EMAIL PROTECTED]> wrote:
Andi Kleen a écrit :
(because of the insane struct file_ra_state f_ra. I wish this structure
were dynamically allocated only for files that really use it)
How about you submit a patch for that instead?
-Andi
On Wed, Aug 17, 2005 at 11:41:29PM -0700, Greg KH wrote:
> On Thu, Aug 18, 2005 at 07:30:50AM +0100, Russell King wrote:
> > On Wed, Aug 17, 2005 at 10:21:56PM -0700, Greg KH wrote:
> > > On Mon, Aug 15, 2005 at 09:32:44AM +0100, Russell King wrote:
> > > > On Mon, Aug 15, 2005 at 01:43:03AM +0100,
Patrick McHardy wrote:
Ollie Wild wrote:
If the ip_append_data() call in icmp_push_reply() fails,
ip_flush_pending_frames() needs to be called. Otherwise, ip_rt_put()
is never called on inet_sk(icmp_socket->sk)->cork.rt, which prevents
the route (and net_device) from ever being freed.
Yo
On Thu, Aug 18, 2005 at 07:30:50AM +0100, Russell King wrote:
> On Wed, Aug 17, 2005 at 10:21:56PM -0700, Greg KH wrote:
> > On Mon, Aug 15, 2005 at 09:32:44AM +0100, Russell King wrote:
> > > On Mon, Aug 15, 2005 at 01:43:03AM +0100, Matthew Wilcox wrote:
> > > > On Sun, Aug 14, 2005 at 11:25:25PM
> > > > We couldn't switch to #2 with patches that simple. They'd in fact
> > > > be rather involved ...
> > >
> > > I'm in favor of #2 on general principle.
> >
> > Which principle would that be, though? :)
>
> it's the basic Linux kernel principle of never disabling interrupts,
> unless reall
On Wed, Aug 17, 2005 at 10:48:05PM -0700, Andrew Morton wrote:
> Pierre Ossman <[EMAIL PROTECTED]> wrote:
> >
> > >I'm thinking that it would be better to not have the config option there
> > >and then re-add it late in the 2.6.14 cycle if someone reports problems
> > >which cannot be fixed. Or
On Wed, Aug 17, 2005 at 10:23:11PM -0700, Greg KH wrote:
> On Mon, Aug 15, 2005 at 05:41:17PM -0500, James Bottomley wrote:
> > Actually, isn't the fix to all of this to combine Greg and James'
> > patches?
>
> Yes it is.
>
> > The Greg one fails in SCSI because we don't have unique class device
On Wed, Aug 17, 2005 at 10:21:56PM -0700, Greg KH wrote:
> On Mon, Aug 15, 2005 at 09:32:44AM +0100, Russell King wrote:
> > On Mon, Aug 15, 2005 at 01:43:03AM +0100, Matthew Wilcox wrote:
> > > On Sun, Aug 14, 2005 at 11:25:25PM +0100, Russell King wrote:
> > > > Eww. Do you really want one struc
On 8/17/05, David Teigland <[EMAIL PROTECTED]> wrote:
> Use configfs to configure lockspace members and node addresses. This was
> previously done with sysfs and ioctl.
>
> Signed-off-by: David Teigland <[EMAIL PROTECTED]>
Are you the official maintainer of the DLM subsystem? Could you submit
a
David Teigland <[EMAIL PROTECTED]> wrote:
>
> Use configfs to configure lockspace members and node addresses. This was
> previously done with sysfs and ioctl.
Fair enough. This really means that the configfs patch should be split out
of the ocfs2 megapatch...
-
To unsubscribe from this list: se
In the dlm I use config_group_find_obj() which isn't exported.
Signed-off-by: David Teigland <[EMAIL PROTECTED]>
diff -urpN a/fs/configfs/item.c b/fs/configfs/item.c
--- a/fs/configfs/item.c2005-08-17 17:19:23.0 +0800
+++ b/fs/configfs/item.c2005-08-18 14:15:51.681973168 +
On 8/17/05, Manfred Spraul <[EMAIL PROTECTED]> wrote:
> Could you try the attached patch? Lots of error are often caused by half
> duplex/full duplex mismatches, and such a bug was just fixed.
Absolutely, it's compiled, I'm testing it right now, if you don't hear
from me in 24 hours it worked :)
On 1/8/05, Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>
> On Fri, 7 Jan 2005, Oleg Nesterov wrote:
> >
> > If i understand this patch correctly, then this code
> >
> > for (;;)
> > write(pipe_fd, &byte, 1);
> >
> > will block after writing PIPE_BUFFERS == 16 characters, no?
>
Use linux/jhash.h instead of our own hash function.
Signed-off-by: David Teigland <[EMAIL PROTECTED]>
---
dir.c |2 +-
dlm_internal.h |1 +
lock.c |2 +-
util.c | 34 --
util.h |2 --
5 files changed, 3 insertion
The reduced member_sysfs.c is no longer related to lockspace members.
Move what's left into lockspace.c which is the only file that uses the
remaining functions.
Signed-off-by: David Teigland <[EMAIL PROTECTED]>
---
Makefile |1
lockspace.c| 155 +
Use configfs to configure lockspace members and node addresses. This was
previously done with sysfs and ioctl.
Signed-off-by: David Teigland <[EMAIL PROTECTED]>
---
drivers/dlm/Makefile |1
drivers/dlm/config.c | 759 -
drivers/dlm/
i have released the 2.6.13-rc6-rt9 tree, which can be downloaded from
the usual place:
http://redhat.com/~mingo/realtime-preempt/
it's a fixes-only release. Changes since 2.6.13-rc6-rt3:
- USB irq flags use cleanups (Alan Stern)
- RCU tasklist-lock fixes (Paul McKenney, Thomas Gleixner)
Pierre Ossman <[EMAIL PROTECTED]> wrote:
>
> >I'm thinking that it would be better to not have the config option there
> >and then re-add it late in the 2.6.14 cycle if someone reports problems
> >which cannot be fixed. Or at least make it default to 'y' so we get more
> >testing coverage, then
Andrew Morton wrote:
>The fact that this is enabled under the experimental
>CONFIG_MMC_BULKTRANSFER seems unfortunate. I mean, if the code works OK
>then we should just enable it unconditionally, no?
>
>
>
It was made this way to make Russell more open to it. I have since not
recieved any more
On Mon, Aug 15, 2005 at 09:32:44AM +0100, Russell King wrote:
> On Mon, Aug 15, 2005 at 01:43:03AM +0100, Matthew Wilcox wrote:
> > On Sun, Aug 14, 2005 at 11:25:25PM +0100, Russell King wrote:
> > > Eww. Do you really want one struct device per tty with all the
> > > memory each one eats?
> > >
On 8/8/05, Kumar Gala <[EMAIL PROTECTED]> wrote:
> (A believe Marcelo would like to see this in 2.6.13, but I'll let him
> fight over that ;)
>
> * Makes dpram allocations work
> * Makes non-console UART work on both 8xx and 82xx
> * Fixed whitespace in files that were touched
>
> Signed-off-by:
On Mon, Aug 15, 2005 at 05:41:17PM -0500, James Bottomley wrote:
> On Sun, 2005-08-14 at 16:02 +0100, Matthew Wilcox wrote:
> > /sys/class/tty/ttyS0/device ->
> > ../../../devices/parisc/0/0:0/pci:00/:00:04.0
> > /sys/class/tty/ttyS1/device ->
> > ../../../devices/parisc/0/0:0/pci:00/
Hi Avuton,
I have not been able to duplicate this without going into standby,
thus this bug may have existed before 2.6.12, as I just started using
ACPI standby.
Could you try the attached patch? Lots of error are often caused by half
duplex/full duplex mismatches, and such a bug was just
Hi,
It appears pci_enable_msi doesn't reconfigure msi registers if it
successfully look up a msi for a device. It assumes the data and address
registers unchanged after calling pci_disable_msi. But this isn't always
true, such as in a suspend/resume circle. In my test system, the
registers unsurpri
Hai..
I want to install 2.2.26 kernel on FC1 (2.4.22) for
testing purpose of my modem..
How can I install it...
regards
aruran
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscri
On Thu, Aug 18, 2005 at 02:58:28PM +1000, Benjamin Herrenschmidt wrote:
> I wonder if it's finally time to implement proper race free list
> iterators in the kernel. Not that difficult... A small struct iterator
> with a list head and the current elem pointer, and the "interated" list
> containing
Wim,
The softdog watchdog timer has a bug that can create an oops:
1. Load the module without the nowayout option.
2. Open the driver and close it without writing 'V' before close.
3. Unload the module. The timer will continue to run...
4. Oops happens when timer fires.
Reported
> I'm not sure why alloc_bootmem is used at all (is the nvram larger than
> a couple of pages on any machine? And if it is, should it really be
> cached in RAM?), but I think it should be sufficient to just use kmalloc
> (well, it works for me).
There used to be cases where we used the nvram stuf
On Thu, 2005-08-18 at 14:33 +1000, Paul Mackerras wrote:
> The PCI error recovery infrastructure needs to be able to contact all
> the drivers affected by a PCI error event, which may mean traversing
> all the devices under a given PCI-PCI bridge. This patch adds a
> function to the PCI core that
* David Brownell <[EMAIL PROTECTED]> wrote:
> > > 1 ALWAYS complete() with IRQs disabled
> > >
> > > 2 NEVER complete() with them disabled
> > >
> > > 3 SOMETIMEs complete() with them disabled.
> > >
> > > Right now we're with #1 which is simple, consistent and guaranteed.
> > >
> > > W
On 229, 08 17, 2005 at 01:14:15PM -0700, Andrew Morton wrote:
> Andrey Panin <[EMAIL PROTECTED]> wrote:
> >
> >
> > This patch adds driver for IBM Automatic Server Restart watchdog hardware
> > found in some IBM eServer xSeries machines. This driver is based on the ugly
> > driver provided by IBM.
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Wed, 17 Aug 2005 21:05:32 -0700
> Perhaps by uprevving the compiler version?
Can't be, we definitely support gcc-2.95 and that compiler
definitely has the bug on sparc64.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
th
The PCI error recovery infrastructure needs to be able to contact all
the drivers affected by a PCI error event, which may mean traversing
all the devices under a given PCI-PCI bridge. This patch adds a
function to the PCI core that traverses all the PCI devices on a PCI
bus and under any PCI-PCI
"David S. Miller" <[EMAIL PROTECTED]> wrote:
>
> From: Andrew Morton <[EMAIL PROTECTED]>
> Date: Wed, 17 Aug 2005 17:38:18 -0700
>
> > I'm prety sure we fixed that somehow. But I forget how.
>
> I wish you could remember :-) I honestly don't think we did.
> The DEFINE_PER_CPU() definition still
> From: Keith Mannthey [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 17, 2005 5:33 PM
>
> On 8/17/05, Davda, Bhavesh P (Bhavesh) <[EMAIL PROTECTED]> wrote:
> > Is there a way to know which task has a particular (struct
> semaphore
> > *) down()ed, leading to another task's down() blocking
On 17.08.2005 [16:35:06 -0700], Andrew Morton wrote:
> Nishanth Aravamudan <[EMAIL PROTECTED]> wrote:
> >
> > Description: Clarify the human-time units to jiffies conversion
> > functions by using the constants in time.h. This makes many of the
> > subsequent patches direct copies of the current co
On Wed, 2005-08-17 at 19:38 -0700, Sundar Narayanaswamy wrote:
> Hi,
> I am trying to experiment using 2.6.12 kernel with the realtime-preempt
> V0.7.51-38 patch to determine the kernel preemption latencies with the
> CONFIG_PREEMPT_RT mode. The test program I wrote does the following on
> a thre
Andi Kleen wrote:
You don't want to always have bad performance though, so you
could attempt to allocate if either the pointer is null _or_ it
points to the global structure?
Remember it's after a GFP_KERNEL OOM. If that fails most likely
you have deadlocked somewhere else already because Lin
Joseph Fannin wrote:
On Thu, Aug 18, 2005 at 02:50:16AM +0200, Bernardo Innocenti wrote:
The relative timestamp reveals that slapd is spending 50ms
after yielding. Meanwhile, GCC is probably being scheduled
for a whole quantum.
Reading the man-page of sched_yield() it seems this isn't
the c
> You don't want to always have bad performance though, so you
> could attempt to allocate if either the pointer is null _or_ it
> points to the global structure?
Remember it's after a GFP_KERNEL OOM. If that fails most likely
you have deadlocked somewhere else already because Linux's handling
of
- FIX: check if the callback is set, before calling it.
- Clean up whitespace / indentation.
Signed-off-by: Patrick Boettcher <[EMAIL PROTECTED]>
Signed-off-by: Michael Krufky <[EMAIL PROTECTED]>
---
linux/drivers/media/dvb/frontends/lgdt330x.c | 50 +--
1 files changed, 25 in
Andi Kleen wrote:
I would just set the ra pointer to a single global structure if the allocation
fails. Then you can avoid all the other checks. It will slow down
things and trash some state, but not fail and nobody should expect good
performance after out of memory anyways. The only check sti
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Wed, 17 Aug 2005 17:38:18 -0700
> I'm prety sure we fixed that somehow. But I forget how.
I wish you could remember :-) I honestly don't think we did.
The DEFINE_PER_CPU() definition still looks the same, and the
way the .data.percpu section is laye
From: Andi Kleen <[EMAIL PROTECTED]>
Date: Thu, 18 Aug 2005 03:05:25 +0200
> I would just set the ra pointer to a single global structure if the
> allocation fails. Then you can avoid all the other checks. It will
> slow down things and trash some state, but not fail and nobody
> should expect goo
On Wed, 2005-08-17 at 20:02 -0400, Steven Rostedt wrote:
> So I went back to the laptop's original config, and did one change. I
> disabled CONFIG_SCHED_SMT, rebooted, and the system booted up. It
> hasn't locked up after four boots. It did once get into some crazy bug
> with scheduling while at
Hi,
I am trying to experiment using 2.6.12 kernel with the realtime-preempt
V0.7.51-38 patch to determine the kernel preemption latencies with the
CONFIG_PREEMPT_RT mode. The test program I wrote does the following on
a thread with highest priority (99) and SCHED_FIFO policy to simulate
a real ti
On Wed, 17 Aug 2005 23:30:13 +0900
Akira Tsukamoto <[EMAIL PROTECTED]> mentioned:
> > I'm trying to understand this mechanism but I don't
> > understand very well.
>
> My explanation was a bit ambiguous, see the code below.
> Where the fp register saved? It saves fp register *inside* task_struct
Joseph Fannin wrote:
>The behavior of sched_yield changed for 2.6. I suppose the man
> page didn't get updated.
Now I remember reading about that on LWN or maybe KernelTraffic.
Thanks!
>>I also think OpenLDAP is wrong. First, it should be calling
>>pthread_yield() because slapd is a multit
(A courteasy CC: on replies would be appreciated, thanks)
Hi!
I get the above oops message (full details below) sometimes when running the
CVS version of "cv", a gtk+ image viewer.
I use kernel 2.6.12.5, but it occured on 2.6.11 that I ran earlier, too.
Unfortunately, it only happens during inte
Wieland Gmeiner <[EMAIL PROTECTED]> writes:
Is there a realistic use case where this new system call is actually useful
and solves something that cannot be solved without it?
If not I think it's better not to merge this to avoid unnecessary bloat.
-Andi
-
To unsubscribe from this list: send the
* Wieland Gmeiner ([EMAIL PROTECTED]) wrote:
> diff -uprN -X linux-2.6.13-rc6-vanilla/Documentation/dontdiff
> linux-2.6.13-rc6-getprlimit/include/linux/security.h
> linux-2.6.13-rc6-setprlimit/include/linux/security.h
> --- linux-2.6.13-rc6-getprlimit/include/linux/security.h 2005-08-17
>
On Wed, Aug 17, 2005 at 02:48:25PM -0700, Jay Vosburgh wrote:
> John W. Linville <[EMAIL PROTECTED]> wrote:
> >Signed-off-by: Jay Vosburg <[EMAIL PROTECTED]>
>
> Pretty close.
>
> Signed-off-by: Jay Vosburgh <[EMAIL PROTECTED]>
Ooops...sorry! Tired, sloppy typing... :-(
> I believ
On 8/18/05, Eric Dumazet <[EMAIL PROTECTED]> wrote:
> Andi Kleen a écrit :
>
> >
> >>(because of the insane struct file_ra_state f_ra. I wish this structure
> >>were dynamically allocated only for files that really use it)
> >
> >
> > How about you submit a patch for that instead?
> >
> > -Andi
>
* Wieland Gmeiner ([EMAIL PROTECTED]) wrote:
> diff -uprN -X linux-2.6.13-rc6-vanilla/Documentation/dontdiff
> linux-2.6.13-rc6-vanilla/kernel/sys.c linux-2.6.13-rc6-getprlimit/kernel/sys.c
> --- linux-2.6.13-rc6-vanilla/kernel/sys.c 2005-08-09 16:03:21.0
> +0200
> +++ linux-2.6.13-rc
On Thu, Aug 18, 2005 at 02:50:16AM +0200, Bernardo Innocenti wrote:
> The relative timestamp reveals that slapd is spending 50ms
> after yielding. Meanwhile, GCC is probably being scheduled
> for a whole quantum.
>
> Reading the man-page of sched_yield() it seems this isn't
> the correct behavior
On Thu, Aug 18, 2005 at 02:40:46AM +0200, Eric Dumazet wrote:
> Andi Kleen a ?crit :
>
> >
> >>(because of the insane struct file_ra_state f_ra. I wish this structure
> >>were dynamically allocated only for files that really use it)
> >
> >
> >How about you submit a patch for that instead?
> >
>
This is the second of two patches, it implements the setprlimit()
syscall.
Implementation: This patch provides a new syscall setprlimit() for
writing a given process resource limits for i386. Its implementation
follows closely the setrlimit syscall. It is given a pid as an
additional argument. If
Hi!
I incorporated the changes suggested by Greg KH and Kyle Moffett and
isolated some duplicated code (between setrlimit/setprlimit resp.
getprlimit/setprlimit) into helper functions. This is the first of
two patches, it implements the getprlimit() call.
Rationale: Currently usage limits (rlimit
On Thu, 18 Aug 2005 10:50 am, Bernardo Innocenti wrote:
> Hello,
>
> I've been investigating a performance problem on a
> server using OpenLDAP 2.2.26 for nss resolution and
> running kernel 2.6.12.
>
> When a CPU bound process such as GCC is running in the
> background (even at nice 10), many triv
Hello,
I've been investigating a performance problem on a
server using OpenLDAP 2.2.26 for nss resolution and
running kernel 2.6.12.
When a CPU bound process such as GCC is running in the
background (even at nice 10), many trivial commands such
as "su" or "groups" become extremely slow and take a
Andi Kleen a écrit :
(because of the insane struct file_ra_state f_ra. I wish this structure
were dynamically allocated only for files that really use it)
How about you submit a patch for that instead?
-Andi
OK, could you please comment this patch ?
The problem of dynamically allocati
"David S. Miller" <[EMAIL PROTECTED]> wrote:
>
> > +DEFINE_PER_CPU(unsigned long, evicted_pages);
>
> DEFINE_PER_CPU() needs an explicit initializer to work
> around some bugs in gcc-2.95, wherein on some platforms
> if you let it end up as a BSS candidate it won't end up
> in the per-cpu section
Fix for manual binding of drivers to devices. Problem is if you pass in
a valid device id, but the driver refuses to bind. Infinite loop as
write() tries to resubmit the data it just sent.
Thanks to Michal Ostrowski <[EMAIL PROTECTED]> for pointing the
problem out.
Signed-off-by: Greg Kroah-Har
Convert users of init_MUTEX and init_MUTEX_LOCKED to
init_mutex and init_mutex_locked - part 4.
Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]>
---
fs/xfs/linux-2.6/xfs_buf.c |4 ++--
kernel/printk.c |2 +-
mm/slab.c|2 +-
net/bluetooth/
When it is supported in BIOS, you will see a HPET line similar to below
in initial ACPI messages.
ACPI: OEMB (v001 A M I AMI_OEM 0x05000510 MSFT 0x0097) @
0xdffdf040
ACPI: HPET (v001 A M I OEMHPET 0x05000510 MSFT 0x0097) @
0xdffd7480
And when it is supported in BIOS, kernel always u
Convert users of init_MUTEX and init_MUTEX_LOCKED to
init_mutex and init_mutex_locked - part 2.
Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]>
---
drivers/infiniband/ulp/ipoib/ipoib_main.c |4 ++--
drivers/input/gameport/gameport.c |2 +-
drivers/input/input.c
Convert users of init_MUTEX and init_MUTEX_LOCKED to
init_mutex and init_mutex_locked - part 1.
Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]>
---
Documentation/i2c/writing-clients|2 +-
arch/arm/oprofile/common.c |2 +-
arch/i386/kernel/ldt.c
Consider the naming of these functions :
sema_init()
init_MUTEX()
init_MUTEX_LOCKED()
init_rwsem()
They are not named very consistent, the naming is confusing and ugly with
the mix of case and some are named init_* and some *_init.
I propose to clean that up by renaming the functions so the
Convert users of init_MUTEX and init_MUTEX_LOCKED to
init_mutex and init_mutex_locked - part 3.
Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]>
---
drivers/s390/net/ctctty.c |2 +-
drivers/s390/s390mach.c |2 +-
drivers/sbus/char/vfc_dev.c |2 +-
drivers
Convert users of sema_init to use init_sema instead.
Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]>
---
arch/ia64/kernel/perfmon.c|2 +-
arch/ia64/kernel/salinfo.c|4 ++--
arch/ia64/sn/kernel/xp_main.c |2 +-
arch/i
This patch renames sema_init to init_sema, init_MUTEX to init_mutex and
init_MUTEX_LOCKED to init_mutex_locked and at the same time creates 3
(deprecated) wrapper functions with the old names.
Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]>
---
include/asm-alpha/semaphore.h | 31
Document sema_init, init_MUTEX & init_MUTEX_LOCKED as being deprecated and
going away in early 2006.
Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]>
---
Documentation/feature-removal-schedule.txt |9 +
1 files changed, 9 insertions(+)
--- linux-2.6.13-rc6-git9-orig/Documentation/fea
On Wed, 2005-08-17 at 18:23 +0200, Ingo Molnar wrote:
> >
> > Using IPI Shortcut mode
> > khelper/794[CPU#0]: BUG in set_new_owner at kernel/rt.c:916
>
> this is a 'must not happen'. Somehow lock->held list got non-empty.
> Maybe some use-after-free thing? Havent seen it myself.
Well, I added
Ollie Wild wrote:
If the ip_append_data() call in icmp_push_reply() fails,
ip_flush_pending_frames() needs to be called. Otherwise, ip_rt_put() is
never called on inet_sk(icmp_socket->sk)->cork.rt, which prevents the
route (and net_device) from ever being freed.
I've attached a patch which f
On Thu, 18 Aug 2005 09:48 am, Peter Williams wrote:
> Con Kolivas wrote:
> > On Thu, 18 Aug 2005 09:15 am, Peter Williams wrote:
> >>Con Kolivas wrote:
> > He did a make allyesconfig which is a bit different and probably far too
> > i/o bound. By the way a single kernel compile is hardly a reproduc
Con Kolivas wrote:
On Thu, 18 Aug 2005 09:15 am, Peter Williams wrote:
Con Kolivas wrote:
On Wed, 17 Aug 2005 18:10, Peter Williams wrote:
Michal Piotrowski wrote:
Hi,
here are schedulers benchmark (part2):
[bits deleted]
Here's a summary of your output generated using the attached Pyth
If a driver's probe function returns -ENXIO or -ENODEV,
driver_probe_device() will translate that to return 0 (comments argue it
is not an error).
Consequently driver_bind() will return 0 resulting in the write
system-call that initiated all of this in returning 0 as well.
If one uses "echo" to
On 8/17/05, Davda, Bhavesh P (Bhavesh) <[EMAIL PROTECTED]> wrote:
> Is there a way to know which task has a particular (struct semaphore *)
> down()ed, leading to another task's down() blocking on it?
I would add a field to struct semaphore that tracks the current process.
In your various up and d
Nishanth Aravamudan <[EMAIL PROTECTED]> wrote:
>
> Description: Clarify the human-time units to jiffies conversion
> functions by using the constants in time.h. This makes many of the
> subsequent patches direct copies of the current code.
>
>
> /* Parameters used to convert the timespec values
On Thu, 18 Aug 2005 09:15 am, Peter Williams wrote:
> Con Kolivas wrote:
> > On Wed, 17 Aug 2005 18:10, Peter Williams wrote:
> >>Michal Piotrowski wrote:
> >>>Hi,
> >>>here are schedulers benchmark (part2):
> >>>[bits deleted]
> >>
> >>Here's a summary of your output generated using the attached P
ALERT!
This e-mail, in its original form, contained one or more attached files that
were infected with a virus, worm, or other type of security threat. This e-mail
was sent from a Road Runner IP address. As part of our continuing initiative to
stop the spread of malicious viruses, Road Runner s
Con Kolivas wrote:
On Wed, 17 Aug 2005 18:10, Peter Williams wrote:
Michal Piotrowski wrote:
Hi,
here are schedulers benchmark (part2):
[bits deleted]
Here's a summary of your output generated using the attached Python script.
| Build Statistics | Overall Statistics
-
On Wed, 2005-08-17 at 21:41 +0400, Stas Sergeev wrote:
> I guess now I realized how you (and Nish)
> assume I could use it: is it that I
> should set CONFIG_HZ to the value I
> need at compile-time, and just remove
> all the timer reprogramming from the
> driver in a hope the dynamic-tick patch
> w
Pierre Ossman <[EMAIL PROTECTED]> wrote:
>
> Adds support for writing multiple sectors at once. This allows
> back-to-back transfers of sectors giving roughly double write throughput.
>
> To be able to detect which sector is causing problems the system falls
> back to single sector writes if a fai
Is there a way to know which task has a particular (struct semaphore *)
down()ed, leading to another task's down() blocking on it?
I'm trying to debug a priority inversion caused by potentially a real
low priority SCHED_OTHER task (potentially a kernel thread like
kjournald) holding an inode->i_se
>Author: Jiri Slaby <[EMAIL PROTECTED]>
>Date: Tue Aug 16 14:35:42 2005 -0700
>
>[WATCHDOG] removes pci_find_device from i6300esb.c
>
>This patch changes
>pci_find_device to pci_get_device (encapsulated in for_each_pci_dev) in
>i6300esb watchdog card with appropriate adding pci_dev_put. Generated i
On 17.08.2005 [12:51:17 -0700], George Anzinger wrote:
> Nishanth Aravamudan wrote:
> ~
> >>IMNSHO we should not get too parental with kernel only interfaces.
> >>Adding 1 is easy enough for the caller and even easier to explain in the
> >>instructions (i.e. this call sleeps for X jiffies edges).
proc_ipmi_root is only defined for CONFIG_PROC_FS, #ifdef it for export as well.
Signed-Off-By: Baruch Even <[EMAIL PROTECTED]>
--
drivers/char/ipmi/ipmi_msghandler.c |2 ++
1 files changed, 2 insertions(+)
Index: k/drivers/char/ipmi/ipmi_msghandler.c
===
Applied.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: "John W. Linville" <[EMAIL PROTECTED]>
Date: Wed, 17 Aug 2005 16:49:59 -0400
> Change operations on rif_lock from spin_{un}lock_bh to
> spin_{un}lock_irq{save,restore} equivalents. Some of the
> rif_lock critical sections are called from interrupt context via
> tr_type_trans->tr_add_rif_inf
John W. Linville <[EMAIL PROTECTED]> wrote:
>Change operations on rif_lock from spin_{un}lock_bh to
>spin_{un}lock_irq{save,restore} equivalents. Some of the
>rif_lock critical sections are called from interrupt context via
>tr_type_trans->tr_add_rif_info. The TR NIC drivers call tr_type_trans
>
On Thu, 18 Aug 2005 04:04, Michal Piotrowski wrote:
> Hi,
> here are additional staircase scheduler benchmarks.
>
> (make all -j8)
>
> scheduler:
> staircase
>
> sched_compute=1
> real49m48.619s
> user77m20.788s
> sys 6m7.653s
Very nice thank you.
Since you are benchmarking, here is
Reference (was):
http://marc.theaimsgroup.com/?l=linux-kernel&m=112421051105982&w=2
Corrections:
1) It is not the 'nvidia' driver, it is the 'forcedeth' ethernet driver
2) It does _not_ only happen after standby, I have finally experienced
errors and drops without going into standby.
Now, with th
From: Brian King <[EMAIL PROTECTED]>
(Looks quite bad, should probably get in right away)
The patch below fixes a bug in the PPC64 iommu vmerge code
which results in the potential for iommu_unmap_sg to go off
unmapping more than it should. This was found on a test system
which resulted in PCI bus
From: Thomas Gleixner <[EMAIL PROTECTED]>
Date: Wed, 17 Aug 2005 22:59:01 +0200
> Shouldn't this be converted to a workqueue, which gets triggered by a
> timer instead of blocking the timer softirq and therefor the delivery of
> other timer functions that long ?
We could, and I'd be happy to appl
On Wed, Aug 17, 2005 at 06:35:03PM +0400, Oleg Nesterov wrote:
> Paul E. McKenney wrote:
> >
> > > The other thing that jumped out at me is that signals are very different
> > > animals from a locking viewpoint depending on whether they are:
> > >
> > > 1.ignored,
> > >
> > > 2.caug
Sorry for sending this twice... The first time I cc'd the wrong email
address for LKML...
Patrick Keene wrote to the linux-dvb list, asking where in menuconfig he
can enable dvb-bt8xx for his AVerMedia DVB card. I pointed the
following out to him:
config DVB_BT8XX
tristate "Nebula/Pin
Change operations on rif_lock from spin_{un}lock_bh to
spin_{un}lock_irq{save,restore} equivalents. Some of the
rif_lock critical sections are called from interrupt context via
tr_type_trans->tr_add_rif_info. The TR NIC drivers call tr_type_trans
from their packet receive handlers.
Signed-off-by
1 - 100 of 227 matches
Mail list logo
