On Sat, 2007-03-10 at 14:42 -0800, Linus Torvalds wrote:
On Sat, 10 Mar 2007, Nicholas Miell wrote:
Care to elaborate on why they're a horrible crock?
It's a *classic* case of an interface that tries to do everything under
the sun.
Here's a clue: look at any system call that takes
On Sat, 10 Mar 2007, Nicholas Miell wrote:
I'd actually much rather do POSIX timers the other way around: associate a
generic notification mechanism with the file descriptor, and then
implement posix_timer_create() on top of timerfd. Now THAT sounds like a
clean unix-like interface
On Wed, Mar 07, 2007 at 07:51:35PM -0800, David Miller wrote:
From: Stephen Hemminger [EMAIL PROTECTED]
Date: Wed, 07 Mar 2007 19:10:47 -0800
David Miller wrote:
What about Willy Tarreau's supposedly even faster variant?
Or does this incorporate that set of improvements?
That's
Simon Arlott [EMAIL PROTECTED] writes:
On 09/03/07 20:42, Francois Romieu wrote:
Simon Arlott [EMAIL PROTECTED] :
When I unplug the cable the system just stops responding to
anything, at all. No message is printed to the console when the
cable is plugged back in.
rtl8139_interrupt
On 10/03/07 13:38, Andi Kleen wrote:
Simon Arlott [EMAIL PROTECTED] writes:
On 09/03/07 20:42, Francois Romieu wrote:
Simon Arlott [EMAIL PROTECTED] :
When I unplug the cable the system just stops responding to
anything, at all. No message is printed to the console when the
cable is plugged
-Original Message-
From: Thomas Graf [mailto:[EMAIL PROTECTED]
Sent: Friday, March 09, 2007 6:35 PM
To: Waskiewicz Jr, Peter P
Cc: Kok, Auke-jan H; David Miller; Garzik, Jeff;
netdev@vger.kernel.org; linux-kernel@vger.kernel.org;
Brandeburg, Jesse; Kok, Auke; Ronciak, John
On Fri, Mar 09, 2007 at 09:42:43PM +0100, Francois Romieu wrote:
Simon Arlott [EMAIL PROTECTED] :
When I unplug the cable the system just stops responding to anything,
at all. No message is printed to the console when the cable is plugged
back in.
rtl8139_interrupt (spin_lock(tp-lock))
I've been thinking a bit more about how useful an absolute timeout is
for a oneshot timer in a virtual environment.
In principle, absolute times are generally preferable. A relative
timeout means timeout in X ns from now, but the meaning of now is
ambiguous, particularly if the vcpu can be
On Mar 8 2007 11:45, Kanhu Rauta wrote:
1in case of fragmention i am getting only one packet at the
hook,While analyzing the ip header it says this is the assembled
packet(skb-len=1528,offset=0,MF=0).
conntrack assembles defragmented packets.
While dumping the data(for 0 to 1528 print
Maybe KERN_DEBUG instead of KERN_ERR?
On 3/10/07, Alan Cox [EMAIL PROTECTED] wrote:
scsi1 : ata_piix
ata2: port disabled. ignoring.
ata2: reset failed, giving up--- THIS IS NEW.
However, I think it's just bogus as there is ata2 is disabled on this laptop.
This is expected behaviour
Alan has been actively working on PATA ACPI, and we have been debugging
ACPI issues as well. PLEASE coordinate with the maintainer, when
touching code outside of drivers/acpi!
ap-cbl is not a reliable way to tell SATA from PATA at the moment. We
need to fix the real crashes too - right now
Hello,
- The wireless changes in here need a lot of testers, please. It is major
rework.
Works for me ... so far ;-) Anyway to the point:
When moving my laptop I reattached the usb mouse. Then I found this in syslog:
usb 2-1: new low speed USB device using uhci_hcd and address 3
usb 2-1:
Hello,
Unable to reproduce so far.
Ok I was wrong. Able to reproduce quite easily. Let me know if you need
anything more.
usb 2-1: new low speed USB device using uhci_hcd and address 11
usb 2-1: new device found, idVendor=046d, idProduct=c00e
usb 2-1: new device strings: Mfr=1, Product=2,
On Sat, 10 Mar 2007 09:33:35 +0100 Mariusz Kozlowski [EMAIL PROTECTED]
wrote:
Hello,
- The wireless changes in here need a lot of testers, please. It is major
rework.
Works for me ... so far ;-) Anyway to the point:
When moving my laptop I reattached the usb mouse. Then I found
On Sat, Mar 10, 2007 at 12:58:28AM -0800, Andrew Morton wrote:
On Sat, 10 Mar 2007 09:33:35 +0100 Mariusz Kozlowski [EMAIL PROTECTED]
wrote:
Hello,
- The wireless changes in here need a lot of testers, please. It is major
rework.
Works for me ... so far ;-) Anyway to the
On Sat, 10 Mar 2007, Greg KH wrote:
hid_parse_report() is doing kmalloc(128k kbytes). We canot sanely
support that and the code shold be rewritten to not do that. A simple
though somewhat lame fix would be to switch to vmalloc().
It's been this way for some time, so it's odd that the
Hello,
On Sat, 10 Mar 2007, Greg KH wrote:
hid_parse_report() is doing kmalloc(128k kbytes). We canot sanely
support that and the code shold be rewritten to not do that. A simple
though somewhat lame fix would be to switch to vmalloc().
It's been this way for some time, so it's
On Sat, 10 Mar 2007, Mariusz Kozlowski wrote:
Right. Can't be 100% sure but without the patch it would have probably
failed by now so I guess the patch is ok. Not sure how to make usb mouse
plugging/unplugging process automatic ;-)
echo FOO /sys/bus/usb/drivers/usbhid/unbind
to
Hello,
Right. Can't be 100% sure but without the patch it would have probably
failed by now so I guess the patch is ok. Not sure how to make usb mouse
plugging/unplugging process automatic ;-)
echo FOO /sys/bus/usb/drivers/usbhid/unbind
to simulate an unplug (actually, to do an
On Sat, 10 Mar 2007, Mariusz Kozlowski wrote:
Hello,
Right. Can't be 100% sure but without the patch it would have probably
failed by now so I guess the patch is ok. Not sure how to make usb mouse
plugging/unplugging process automatic ;-)
echo FOO
On Sat, Mar 10, 2007 at 10:01:21AM +0100, Ingo Molnar wrote:
* Pavel Machek [EMAIL PROTECTED] wrote:
s2ram should be able to work around this, it has parts from
radeontool. (suspend.sf.net).
i'm wondering, do you have any idea how Windows handles the
suspend/resume quirks problem
On Sat, Mar 10, 2007 at 12:43:01PM +0100, Stefan Seyfried wrote:
On Sat, Mar 10, 2007 at 10:01:21AM +0100, Ingo Molnar wrote:
i'm wondering, do you have any idea how Windows handles the
suspend/resume quirks problem area? Do they curse BIOS vendors and
maintain a large DB of DMI-driven
* Stefan Seyfried [EMAIL PROTECTED] wrote:
btw., the s2ram database seems quite a bit spotty:
$ ./s2ram -n
Machine is unknown.
This machine can be identified by:
sys_vendor = System manufacturer
sys_product = System Product Name
sys_version = System Version
Hi!
Ok. To be honest, you are the first reporter that seems to have read
the documentation above, but not understood what to do.
thanks for the compliment ;-) _I_ very much know what to do (i mailed
the right person after all ;), but i dont really count and on the 6
(Can we get the
On Sat, 2007-03-10 at 17:16 -0500, Robert P. J. Day wrote:
Delete apparently unused header file drivers/scsi/pci2000.h.
This was apparently missed by Christoph when he removed the driver ...
I'll add it to the queue. For future SCSI work, could you cc
linux-scsi@vger.kernel.org please? That
On 3/11/07, Con Kolivas [EMAIL PROTECTED] wrote:
Has anyone had any trouble with RSDL on the stable kernels (ie not -mm)?
Tested fine so far on ppc, ia64 and (mostly) parisc.
HTH
--
Thibaut VARENE
http://www.parisc-linux.org/~varenet/
-
To unsubscribe from this list: send the line
On 3/11/07, Thibaut VARENE [EMAIL PROTECTED] wrote:
On 3/11/07, Con Kolivas [EMAIL PROTECTED] wrote:
Has anyone had any trouble with RSDL on the stable kernels (ie not -mm)?
Tested fine so far on ppc, ia64 and (mostly) parisc.
I meant ppc64, actually.
Gomen.
--
Thibaut VARENE
On Sat, Mar 10, 2007 at 04:21:01PM -0800, Andrew Morton wrote:
On Sat, 10 Mar 2007 10:33:41 -0800 Kees Cook [EMAIL PROTECTED] wrote:
Here's another revision, with both the can ptrace and the global /proc
knob;
We'd be needing a changelog for that.
Please update the procfs
The /proc/pid/ maps, smaps, and numa_maps files contain sensitive
information about the memory location and usage of processes. Issues:
- maps should not be world-readable, especially if programs expect any
kind of ASLR protection from local attackers.
- maps cannot just be 0400 because
I've tested -mm2 against -mm2+noyield and -mm2+rsdl+noyield. The
noyield patch simply makes the sched_yield syscall return immediately.
Xorg and all tests are run at nice 0.
Loads:
memload: constant memcpy of 16MB buffer
execload: constant re-exec of a trivial shell script
forkload: constant
On Sat, 2007-03-10 at 16:35 -0800, Linus Torvalds wrote:
On Sat, 10 Mar 2007, Nicholas Miell wrote:
I'd actually much rather do POSIX timers the other way around: associate
a
generic notification mechanism with the file descriptor, and then
implement posix_timer_create() on
On Sat, Mar 10, 2007 at 04:21:01PM -0800, Andrew Morton wrote:
We'd be needing a changelog for that.
Done; sent separately from this email.
Please update the procfs documentation.
Done.
Does the patch also cover /proc/pid/smaps?
Yes, and numa_maps.
Thanks!
--
Kees Cook
-
To unsubscribe
On Sat, 10 Mar 2007, Nicholas Miell wrote:
If that's the goal, somebody should start thinking about reducing the
contents of struct file to the bare minimum (i.e. not much more than a
file_operations pointer).
That's already pretty smal, and the single inode (and maybe dentry) will
make it
On Sat, 2007-03-10 at 17:57 -0800, Davide Libenzi wrote:
On Sat, 10 Mar 2007, Nicholas Miell wrote:
If that's the goal, somebody should start thinking about reducing the
contents of struct file to the bare minimum (i.e. not much more than a
file_operations pointer).
That's already
Add slub_max_order
Avoid slabs getting to large. Do no longer enforce slub_min_objects
if the slab gets bigger than slub_max_order.
I am not sure if we really want this. Maybe we should make the
selection of the base page size depending on page allocator
defrag behavior? I.e. try to restrict
[PATCH] SLUB The unqueued slab allocator v4
V4-V5:
- Single object slabs only for slabs slub_max_order otherwise generate
sufficient objects to avoid frequent use of the page allocator. This is
necessary to compensate for fragmentation caused by frequent uses of
the page allocator. We
Enable poisoning / redzoning for slabs with constructors or SLAB_DEWSTROY_BY_RCU
We cannot poison the object itself but we can poison padding spaces and do
the redzoning. For that we introduce another flag controlling object
poisoning.
Signed-off-by: Christoph Lameter [EMAIL PROTECTED]
Index:
This patch add an anonymous inode source, to be used for files that need
and inode only in order to create a file*. We do not care of having an
inode for each file, and we do not even care of having different names in
the associated dentries (dentry names will be same for classes of file*).
This patch series implements the new signalfd() system call.
I took part of the original Linus code (and you know how
badly it can be broken :), and I added even more breakage ;)
Signals are fetched from the same signal queue used by the process,
so signalfd will compete with standard kernel
This patch wire the signalfd system call to the i386 architecture.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.20.ep2/arch/i386/kernel/syscall_table.S
===
---
This patch wire the signalfd system call to the x86_64 architecture.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.20.ep2/include/asm-x86_64/unistd.h
===
---
This patch introduces a new system call for timers events delivered
though file descriptors. This allows timer event to be used with
standard POSIX poll(2), select(2) and read(2). As a consequence of
supporting the Linux f_op-poll subsystem, they can be used with
epoll(2) too.
The system call is
This patch implement the necessary compat code for the signalfd system call.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.20.ep2/fs/compat.c
===
--- linux-2.6.20.ep2.orig/fs/compat.c
This patch wire the timerfd system call to the i386 architecture.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.20.ep2/arch/i386/kernel/syscall_table.S
===
---
This patch wire the timerfd system call to the x86_64 architecture.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.20.ep2/arch/x86_64/ia32/ia32entry.S
===
---
This patch implement the necessary compat code for the timerfd system call.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.20.ep2/fs/compat.c
===
--- linux-2.6.20.ep2.orig/fs/compat.c
On 11/03/07, Matt Mackall [EMAIL PROTECTED] wrote:
I've tested -mm2 against -mm2+noyield and -mm2+rsdl+noyield. The
noyield patch simply makes the sched_yield syscall return immediately.
Xorg and all tests are run at nice 0.
Loads:
memload: constant memcpy of 16MB buffer
execload: constant
On Sat, 2007-03-10 at 02:31 -0200, Mauro Carvalho Chehab wrote:
From: Trent Piepho [EMAIL PROTECTED]
When a module uses symbol_get() to increase the ref count of another
module, there is no record what module called symbol_get(). A module
can
show up as having other users, but there is no
On Sat, 2007-03-10 at 02:04 +0100, Jan Engelhardt wrote:
Getting back at the macro, how would you like to have it merged?
Well, this is what I sent to Linus and Andrew (many thanks to those who
made appropriately whimsical *or* useful comments):
diff -r 1ccdf46b0f41 include/linux/compiler-gcc.h
This patchset introduces an arch independent framework to handle lists
of recently used page table pages.
Page table pages have the characteristics that they are typically zero
or in a known state when they are freed. This is usually the exactly
same state as needed after allocation. So it makes
Abstract quicklist from the IA64 implementation
Extract the quicklist implementation for IA64, clean it up
and generalize it to:
1. Allow multiple quicklists
2. Add support for constructors and destructors..
Quicklist allocation and frees occur inline. The support
for constructors /
x86_64: Convert to use a single quicklists
This adds caching of pgds and puds, pmds, pte. That way we can
avoid costly zeroing and initialization of special mappings in the
pgd.
The first patch just adds a simple implementation using a single
quicklist. As a consequence we need to zero a pgd
i386: Convert to quicklists
Implement the i386 management of pgd and pmds using quicklists.
The i386 management of page table pages currently uses page sized slabs.
The page state is therefore mainly determined by the slab code. However,
i386 also uses its own fields in the page struct to mark
Slub: Remove special casing for page sized slabs
After we have used quicklist so that arches can avoid using the slab
allocator to manage page table pages we can now remove the special
casing from slub.
This is against SLUB V5
Signed-off-by: Christoph Lameter [EMAIL PROTECTED]
Index:
x86_64: Add quicklist for pgd.
A second quicklist is useful to separate out PGD handling. We can carry
the initialized pgds over to the next process needing them. This
avoids the zeroing of the pgds on free that we had to introduce
in the last patch.
Also clean up the pgd_list handling to use
i386: Use standard list macros.
Get rid of generating a list via page-index and page-private. Use
page-lru instead.
Signed-off-by: Christoph Lameter [EMAIL PROTECTED]
Index: linux-2.6.21-rc3/arch/i386/mm/pgtable.c
===
---
On Sat, 2007-03-10 at 14:52 -0800, Jeremy Fitzhardinge wrote:
When booting under Xen, you'll get this if you're using both the xen
clocksource and clockevent drivers. However, it seems that during boot
on a NO_HZ HIGHRES_TIMERS system, the kernel does not use the Xen
clocksource until it
Thomas Gleixner wrote:
The clocksource is not used until the clocksource is installed. Also the
periodic mode during boot, when the clock event device supports periodic
mode, is not reading the time. It relies on the clock event device
getting it straight.
Yes. This could be one source of
Thomas Gleixner wrote:
It's simply enforced in NO_HZ, HIGHRES mode as we operate in absolute
time, which is read back from the clocksource, even if we use a relative
value for real hardware clock event devices to program the next event.
We calculate the delta between the absolute event and
* Pavel Machek [EMAIL PROTECTED] wrote:
Even if one doesn't use the fb console at all, radeonfb apparently
is still required on some ThinkPad models to work around BIOS bugs:
http://www.thinkwiki.org/wiki/Problem_with_high_power_drain_in_ACPI_sleep#Radeon_GPU_not_powered_off
s2ram
Hi!
Even if one doesn't use the fb console at all, radeonfb apparently
is still required on some ThinkPad models to work around BIOS bugs:
http://www.thinkwiki.org/wiki/Problem_with_high_power_drain_in_ACPI_sleep#Radeon_GPU_not_powered_off
s2ram should be able to work around
On Mar 11 2007 13:50, Rusty Russell wrote:
On Sat, 2007-03-10 at 02:04 +0100, Jan Engelhardt wrote:
Getting back at the macro, how would you like to have it merged?
Well, this is what I sent to Linus and Andrew (many thanks to those who
made appropriately whimsical *or* useful comments):
diff
On Sun, 11 Mar 2007 13:28:22 +1100 Con Kolivas [EMAIL PROTECTED] wrote:
Well... are you advocating we change sched_yield semantics to a
gentler form?
From a practical POV: our present yield() behaviour is so truly awful that
it's basically always a bug to use it. This probably isn't a good
On Sun, 2007-03-11 at 03:58 +0100, Jan Engelhardt wrote:
-#define ARRAY_SIZE(x) (sizeof(x) / sizeof((x)[0]))
+#define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) +
__must_be_array(arr))
+
80 cols *cough* :)
I think your cough added a column?
Rusty.
-
To unsubscribe from this list:
On Sunday 11 March 2007 14:16, Andrew Morton wrote:
On Sun, 11 Mar 2007 13:28:22 +1100 Con Kolivas [EMAIL PROTECTED]
wrote: Well... are you advocating we change sched_yield semantics to a
gentler form?
From a practical POV: our present yield() behaviour is so truly awful that
it's
Hi,
Since linux 2.6.20 the kernel log shows at boot time these error. The
system are stable, but shows this, that in 2.6.19.N does not show.
(please CC to my email, i am currently not subscribe to lkml)
Thanks,
Linux version 2.6.20.2 ([EMAIL PROTECTED]) (gcc version 3.4.6) #1 PREEMPT Fri
Mar
On Sun, 11 Mar 2007 14:59:28 +1100 Con Kolivas [EMAIL PROTECTED] wrote:
Bottom line: we've had a _lot_ of problems with the new yield() semantics.
We effectively broke back-compatibility by changing its behaviour a lot,
and we can't really turn around and blame application developers for
On Sat, 10 Mar 2007, Linus Torvalds wrote:
(That said, using struct itimerspec might be a good idea. That would
also obviate the need for TFD_TIMER_SEQ, since an itimerspec automatically
has both base and incremental parts).
But TFD_TIMER_SEQ is a simple auto-rearm case of TFD_TIMER_REL. So
On Sun, 11 Mar 2007 13:28:22 +1100 Con Kolivas [EMAIL PROTECTED] wrote:
Well... are you advocating we change sched_yield semantics to a
gentler form?
On Sat, Mar 10, 2007 at 07:16:14PM -0800, Andrew Morton wrote:
From a practical POV: our present yield() behaviour is so truly awful that
it's
On Sunday 11 March 2007 14:39, Andrew Morton wrote:
On Sun, 11 Mar 2007 14:59:28 +1100 Con Kolivas [EMAIL PROTECTED] wrote:
Bottom line: we've had a _lot_ of problems with the new yield()
semantics. We effectively broke back-compatibility by changing its
behaviour a lot, and we can't
What follows this email is a patch series for the latest version of the RSDL
cpu scheduler (ie v0.29). I have addressed all bugs that I am able to
reproduce in this version so if some people would be kind enough to test if
there are any hidden bugs or oops lurking, it would be nice to know in
From: Con Kolivas [EMAIL PROTECTED]
Add a list_splice_tail variant of list_splice.
Patch-by: Peter Zijlstra [EMAIL PROTECTED]
Signed-off-by: Con Kolivas [EMAIL PROTECTED]
Cc: Ingo Molnar [EMAIL PROTECTED]
Cc: Nick Piggin [EMAIL PROTECTED]
Cc: Siddha, Suresh B [EMAIL PROTECTED]
Signed-off-by:
From: Con Kolivas [EMAIL PROTECTED]
Remove the sleep_avg field from proc output as it will be removed from the
task_struct.
Signed-off-by: Con Kolivas [EMAIL PROTECTED]
Cc: Ingo Molnar [EMAIL PROTECTED]
Cc: Nick Piggin [EMAIL PROTECTED]
Cc: Siddha, Suresh B [EMAIL PROTECTED]
Signed-off-by:
From: Con Kolivas [EMAIL PROTECTED]
Remove the TASK_NONINTERACTIVE flag as it will no longer be used.
Signed-off-by: Con Kolivas [EMAIL PROTECTED]
Cc: Ingo Molnar [EMAIL PROTECTED]
Cc: Nick Piggin [EMAIL PROTECTED]
Cc: Siddha, Suresh B [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL
From: Con Kolivas [EMAIL PROTECTED]
Modify the sched_find_first_bit function to work on a 180bit long bitmap.
Signed-off-by: Con Kolivas [EMAIL PROTECTED]
Cc: Ingo Molnar [EMAIL PROTECTED]
Cc: Nick Piggin [EMAIL PROTECTED]
Cc: Siddha, Suresh B [EMAIL PROTECTED]
Signed-off-by: Andrew Morton
The practice of renicing kernel threads to negative nice values is of
questionable benefit at best, and at worst leads to larger latencies when
kernel threads are busy on behalf of other tasks.
Signed-off-by: Con Kolivas [EMAIL PROTECTED]
---
kernel/workqueue.c |1 -
1 file changed, 1
From: Con Kolivas [EMAIL PROTECTED]
Add comprehensive documentation of the RSDL cpu scheduler design.
Signed-off-by: Con Kolivas [EMAIL PROTECTED]
Cc: Ingo Molnar [EMAIL PROTECTED]
Cc: Nick Piggin [EMAIL PROTECTED]
Cc: Siddha, Suresh B [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL
On Sun, Mar 11, 2007 at 01:28:22PM +1100, Con Kolivas wrote:
make -j 5 ccache
berylok good awful
galeon goodgood bad
mp3 goodgood bad
terminal goodgood bad/ok
mousegoodgood bad/ok
On Sat, Mar 10, 2007 at 10:01:32PM -0600, Matt Mackall wrote:
On Sun, Mar 11, 2007 at 01:28:22PM +1100, Con Kolivas wrote:
Ok I don't think there's any actual accounting problem here per se
(although I did just recently post a bugfix for rsdl however I think
that's unrelated). What I think
On Saturday 10 March 2007 5:13 am, Haavard Skinnemoen wrote:
This is a very simple bitbanging i2c bus driver utilizing the new
arch-neutral GPIO API. ...
---
This patch is different from the first patch in the following ways:
* Handles pins set up as open drain (aka multidrive) by toggling
On Saturday 10 March 2007 12:15 pm, Jean Delvare wrote:
Hi Haavard,
On Sat, 10 Mar 2007 14:13:28 +0100, Haavard Skinnemoen wrote:
This is a very simple bitbanging i2c bus driver utilizing the new
arch-neutral GPIO API. Useful for chips that don't have a built-in
i2c controller,
On Sat, Mar 10, 2007 at 06:09:34PM -0800, Christoph Lameter wrote:
i386: Convert to quicklists
Implement the i386 management of pgd and pmds using quicklists.
I approve, though it would be nice if ptes had an interface operating
on struct page * to use.
On Sat, Mar 10, 2007 at 06:09:34PM
On Saturday 10 March 2007 06:30, Jeff Garzik wrote:
Linux Kernel Mailing List wrote:
Gitweb:
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=df33c77e3981e71afc8727ee5c432ba1a1bba68c
Commit: df33c77e3981e71afc8727ee5c432ba1a1bba68c
Parent:
Hi all,
Here is an update for RSDL to version 0.28
Full patch:
http://ck.kolivas.org/patches/staircase-deadline/2.6.20-sched-
rsdl-0.28.patch
Series:
http://ck.kolivas.org/patches/staircase-deadline/2.6.20/
The patch to get you from 0.26 to 0.28:
Hello, again,
I just saw that my 0.28 patch file was wrongly named 0.26 and that there is a
new version 0.29 of RSDL that just came out... so here is the backported RSDL
0.29 to a 2.6.18.8 kernel.
This does compile but I did not got the time to fully test it yet.
Here is an update for RSDL
Sam Ravnborg [EMAIL PROTECTED] wrote:
On Sat, Mar 10, 2007 at 10:34:41PM +0100, Jan Engelhardt wrote:
On Mar 10 2007 22:27, Sam Ravnborg wrote:
On Sat, Mar 10, 2007 at 07:23:41PM +0100, Jan Engelhardt wrote:
Whether the 'working config file path' should change when you do
'Save as
On Sat, 10 Mar 2007, Nicholas Miell wrote:
Ah, I see. You're just interested in fds as a generic handle concept,
and not a more Plan 9 type thing.
Indeed. It's a handle.
UNIX has pid's for process handles, and file descriptors for just
about everything else.
If that's the goal, somebody
On Sat, 10 Mar 2007, Davide Libenzi wrote:
On Sat, 10 Mar 2007, Linus Torvalds wrote:
(That said, using struct itimerspec might be a good idea. That would
also obviate the need for TFD_TIMER_SEQ, since an itimerspec automatically
has both base and incremental parts).
But
On Sat, 10 Mar 2007, Linus Torvalds wrote:
Actually, the only place where I can find the itimerspec usefull, is
indeed with TFD_TIMER_SEQ. In cases where you want you clock starting at a
given time (it_value) *and* with the given frequency (it_interval).
.. and this is where itimerspec
On Fri, 2007-03-09 at 21:41 -0800, Linus Torvalds wrote:
On Sat, 10 Mar 2007, Sergio Monteiro Basto wrote:
With this quirk I got this oops on hibernate (but computer still
working)
Well, strictly speaking it's a warning, not an oops per se.
What happens is that the quirk wants to
On Sat, 2007-03-10 at 21:31 -0800, Linus Torvalds wrote:
On Sat, 10 Mar 2007, Nicholas Miell wrote:
Ah, I see. You're just interested in fds as a generic handle concept,
and not a more Plan 9 type thing.
Indeed. It's a handle.
UNIX has pid's for process handles, and file
On Sunday 11 March 2007 15:03, Matt Mackall wrote:
On Sat, Mar 10, 2007 at 10:01:32PM -0600, Matt Mackall wrote:
On Sun, Mar 11, 2007 at 01:28:22PM +1100, Con Kolivas wrote:
Ok I don't think there's any actual accounting problem here per se
(although I did just recently post a bugfix for
Is this safe to think about applying yet?
We lost the leak detector feature.
It might be nice to create synonyms for PageActive, PageReferenced and
PageError, to make things clearer in the slub core. At the expense of
making things less clear globally. Am unsure.
-
To unsubscribe from this
On Sat, 10 Mar 2007, Andrew Morton wrote:
Is this safe to think about applying yet?
Its safe. By default kernels will be build with SLAB. SLUB becomes only a
selectable alternative. It should not become the primary slab until we
know that its really superior overall and have thoroughly tested
Good Day
Say i want to implement extended set of ATA commands available to
userspace for building diagnostic tools.
I need 0x40 -- read verify and 0x32 -- write long with error handling,
for example. I was trying ide driver through ioctl's, but seems it
lack of functionality and full of gotchas.
DISCLAIMER: This patch is still experimental.
AUTHOR: Rudolf Marek has written the coretemp module for Intel Core Duo/Solo
processors.
Without this patch, you cannot monitor your CPU temperature, at least not
on a DG965 motherboard.
From the readme (second patch):
+Kernel driver coretemp
On Sat, 10 Mar 2007 17:27:44 -0500 (EST) Robert P. J. Day [EMAIL
PROTECTED] wrote:
Delete apparently unused header file
sound/pci/cs46xx/imgs/cwcemb80.h.
That patch series was rather a mess
- Multiple patches with the same Subject: (I might have lost some as a result)
- Several
On Sat, Mar 10, 2007 at 07:35:06PM -0600, Matt Mackall wrote:
I've tested -mm2 against -mm2+noyield and -mm2+rsdl+noyield. The
noyield patch simply makes the sched_yield syscall return immediately.
Xorg and all tests are run at nice 0.
[skipped long and precise test report]
Also note I could
[Sam Ravnborg - Sat, Mar 10, 2007 at 11:45:34PM +0100]
| On Sat, Mar 10, 2007 at 10:34:41PM +0100, Jan Engelhardt wrote:
|
| On Mar 10 2007 22:27, Sam Ravnborg wrote:
| On Sat, Mar 10, 2007 at 07:23:41PM +0100, Jan Engelhardt wrote:
|
| Whether the 'working config file path' should change
[Bodo Eggert - Sun, Mar 11, 2007 at 06:21:59AM +0100]
| Sam Ravnborg [EMAIL PROTECTED] wrote:
| On Sat, Mar 10, 2007 at 10:34:41PM +0100, Jan Engelhardt wrote:
| On Mar 10 2007 22:27, Sam Ravnborg wrote:
| On Sat, Mar 10, 2007 at 07:23:41PM +0100, Jan Engelhardt wrote:
|
| Whether the
401 - 500 of 502 matches
Mail list logo
