On Tue, 2007-04-03 at 07:31 +0200, Mike Galbraith wrote:
On Tue, 2007-04-03 at 12:37 +1000, Con Kolivas wrote:
On Thursday 29 March 2007 15:50, Mike Galbraith wrote:
On Thu, 2007-03-29 at 09:44 +1000, Con Kolivas wrote:
+ * This contains a bitmap for each dynamic priority level with empty
* Mike Galbraith [EMAIL PROTECTED] wrote:
Try two instances of chew.c at _differing_ nice levels on one cpu on
mainline, and then SD. This is why you can't renice X on mainline.
How about something more challenging instead :)
The numbers below are from my scheduler tree with
On Tue, 3 Apr 2007 15:44:19 +1000 David Chinner [EMAIL PROTECTED] wrote:
In XFS, one of the shrinkers cwthat gets registered calls causes all
the xfsbufd's in the system to run and write back delayed write
metadata - this can't be freed up until it is clean, and this is the
only hook we have
The generic networking code ensures that no two networking devices
have the same name, so there is no time except when sysfs has
implementation bugs that device_rename when called from
dev_change_name will fail.
The current error handling for errors from device_rename in
dev_change_name is
On Tue, 03 Apr 2007 15:47:05 +1000 Rusty Russell [EMAIL PROTECTED] wrote:
On Mon, 2007-04-02 at 21:57 -0700, Andrew Morton wrote:
On Tue, 03 Apr 2007 14:45:02 +1000 Rusty Russell [EMAIL PROTECTED] wrote:
Does that mean the to function correctly every user needs some internal
cursor so it
On Tue, 2007-04-03 at 08:01 +0200, Ingo Molnar wrote:
* Mike Galbraith [EMAIL PROTECTED] wrote:
Try two instances of chew.c at _differing_ nice levels on one cpu on
mainline, and then SD. This is why you can't renice X on mainline.
How about something more challenging instead :)
On Mon, 2007-04-02 at 19:09 +0200, Marco wrote:
Marco ha scritto:
Any idea? :'(
Not sure why your /proc/mtrr output is like that, but if you want vesafb
to use mtrr, use:
video=vesafb:mtrr:3,ywrap... instead
(See Documentation/fb/vesafb.txt)
Tony
-
To unsubscribe from this list: send
On Mon, Apr 02, 2007 at 11:01:58PM -0700, Andrew Morton wrote:
On Tue, 3 Apr 2007 15:44:19 +1000 David Chinner [EMAIL PROTECTED] wrote:
In XFS, one of the shrinkers cwthat gets registered calls causes all
the xfsbufd's in the system to run and write back delayed write
metadata - this
On Tue, 3 Apr 2007 01:04:05 -0400, Dmitry Torokhov [EMAIL PROTECTED] wrote:
What do you think?
The patch looks sane, although I haven't yet tested it. I'll live with
it until next quarterly update, then consider if I should take it or use
my patch for RHEL 5 and RHEL 4.
-- Pete
-
To
* Ayaz Abdulla [EMAIL PROTECTED] wrote:
I had responded eariler to the thread asking you to try out the patch
found in bug 8058:
http://bugzilla.kernel.org/show_bug.cgi?id=8058
I believe that is the caush of the NULL skb dereference issue.
there's a different type of regression now: under
* David Sperry [EMAIL PROTECTED] wrote:
I think there is some kind of bad behavior happening in the Nvidia
driver with respect to softirq-net-tx and IRQ-8406.
yes. Part of the problem is that the forcedeth.c driver does not
fully support NAPI - today i've implemented those bits
Hi all, I've bought a USB wireless TA bundled with GPL
Linux drivers for 2.6.11 kernel series.
Hi. Maybe I can help u providing some http space. I also bought Conitech Dakota
Wireless TA 56Mbps but drivers are currently not working: my version is
hal_059...
-
To unsubscribe from this list:
On 02-04-2007 21:41, Christian Kujau wrote:
Hi there,
we have serious problems with 2 of our servers: both shiny new amd64
dual core, with both 2GB RAM, 32bit kernel+userland (Debian/testing).
Both servers have 2 NICs, RTL8139 (eth0, irq10) and RTL8169s
(eth1, irq11).
Hi,
Did you try
* Ingo Molnar [EMAIL PROTECTED] wrote:
I had responded eariler to the thread asking you to try out the patch
found in bug 8058:
http://bugzilla.kernel.org/show_bug.cgi?id=8058
I believe that is the caush of the NULL skb dereference issue.
there's a different type of regression
On Mon, 2007-04-02 at 23:09 -0700, Andrew Morton wrote:
hm, well, six-of-one, VI of the other. We save maybe four kmallocs across
the entire uptime at the cost of exposing stuff kernel-side which doesn't
need to be exposed.
This is not about efficiency. When have I *ever* posted optimization
Hi Bob,
On Mon, 2 Apr 2007 13:55:49 -0700, Moore, Robert wrote:
The ACPI specification allows concurrent execution of control methods
although methods cannot be preempted. The ACPICA interpreter mutex is
used to implement this model.
From section 5.5.2, Control Method Execution:
I'm using Linux 2.6.20.4. I noticed that I get lower SATA hard drive
throughput with 2.6.20.4 than with 2.6.19. The reason was that 2.6.20
enables NCQ by defauly (queue_depth = 31/32 instead of 0/32). Transfer rate
was measured using hdparm -t:
With NCQ (queue_depth == 31): 50MB/s.
Without
Christoph Lameter wrote:
SLUB Core patch V6
This provides basic SLUB functionality and allows a choice of
slab allocators during kernel configuration. The default is still
slab. SLUB has been tested in various configurations but I think we
can be quite sure that there are still remaining
On Sat, Mar 24, 2007 at 08:35:35AM +0530, Maneesh Soni wrote:
On Fri, Mar 23, 2007 at 12:43:27PM -0700, Ethan Solomita wrote:
I ran stress testing overnight and came up with a similar failure
(s_dentry == NULL) but in a different location. A NULL pointer
dereference happened in
Rafael J. Wysocki napsal(a):
On Monday, 2 April 2007 10:24, Jiri Slaby wrote:
Rafael J. Wysocki napsal(a):
On Thursday, 29 March 2007 09:44, Jiri Slaby wrote:
swsusp: critical section:
swsusp: Need to copy 131380 pages
swsusp: Not enough free memory
Error -12 suspending
Enabling non-boot
I'm working on getting the IDE subsystem to communicate with an IDE
device wired to nCS5 on a CLEP7312 board. I have
0x5000 set to be remapped to 0xfe10 but whenever I try to access the
registers I get kernel crashes. I'm sure I'm doing
something wrong, since this works on a
This is a simplified and actually more comprehensive form of a bug
fix from Mitch Williams [EMAIL PROTECTED].
When we mask or unmask a msi-x irqs the writes may be posted because
we are writing to memory mapped region. This means the mask and
unmask don't happen immediately but at some
On Mon, Apr 02, 2007 at 10:48:24PM +0200, Rafael J. Wysocki wrote:
On Monday, 2 April 2007 15:56, Pavel Machek wrote:
Hi!
This patch provides an interface to extend the use of the process
freezer beyond Suspend.
The tasks can selectively mark themselves to be exempted from
what is the real advantage to package uml-kernel and rootfs into a single
file ?
If this needs to be distributed with additional script, that's two files,
anyway.
the classical way would be 3 files: uml-kernel, rootfs, script - put into
some tar.gz or tar.bz2
this could look as elegant
On Monday 02 April 2007 23:12, Andi Kleen wrote:
How would that work in the case where virtualized guests don't have a
visible PCI bus, and the virtual environment doesn't pretend to emulate
a PCI bus?
If they emulated one with the appropiate device
then distribution driver auto
On Tuesday 03 April 2007 10:29:06 Christian Borntraeger wrote:
On Monday 02 April 2007 23:12, Andi Kleen wrote:
How would that work in the case where virtualized guests don't have a
visible PCI bus, and the virtual environment doesn't pretend to emulate
a PCI bus?
If they
Hello,
I'm not sure whether a fix is necessary for the following scenario.
The kernel configure target make menuconfig requires ncurses. FWIW, it
could probably be better if the error message would indicate that that
ncurses is necessary for make menuconfig to run and that the user could
be
On Mon, 2 Apr 2007, Pete Zaitcev wrote:
How about this?
Looks quite fine to me.
But in case that Dmitry's patch Input: add generic suspend and resume for
uinput devices fixes your issue too, I wouldn't merge it as it won't be
needed. Could you please let me know?
@@ -947,6 +989,8 @@ static
On Mon, 2 Apr 2007 09:59:28 -0700,
David Brownell [EMAIL PROTECTED] wrote:
But long term, I wonder. Isn't no kevents issued an extremely
blunt tool, which could cause lots of damage? It might be better
to have selective filters, one per event family: core (add/remove),
online/offline,
* David Sperry [EMAIL PROTECTED] wrote:
there are a few other things i'm working on to improve this. I've
uploaded -rt9 which is the current state of affairs. Note that using
-rt9 you'll likely only see IRQ-8406 overhead in the system, because
i've added an optimization to do process
On Tue, 3 Apr 2007, Li Yu wrote:
What's the position of hidraw? It only is used when all other driver is
not usable on some report? or, it should be stick every working device.
Current implementation (as you can see it in -mm or in my hid.git tree) is
creating hidraw interface for just every
On Tue, 3 Apr 2007, Li Yu wrote:
May be, we need some means to change blacklist in runtime.
Paul Walmsley (added to CC) sent me patches some time ago that among other
things implemented possibility to modify the hid_blacklist[] in runtime.
The patches had some issues which Paul said will fix
Jiri Kosina wrote:
As this quirk is only needed once in the initialization method, we could
probably get rid of it and just put and explicit test for PID and VID
there (with apropriate comment). We can't afford wasting quirk entries, as
we are slowly running out of them.
Is it a problem of
Rusty Russell [EMAIL PROTECTED] writes:
2) The wrapper code in xfs might no longer be needed.
3) The placing in the x86-64 hot function list for seems a little
unlikely. Clearly, Andi was testing if anyone was paying attention.
That came from Arjan. The list is likely quite out of date now
On Saturday 31 March 2007, Neil Brown wrote:
Code: 44 89 74 24 48 0f 20 c6 0f 06 0f 11 04 24 0f 11 4c 24 10 0f 11 54
24 20 0f
11 5c 24 30 0f 18 82 00 01 00 00 0f 18 82 20 01 00 00 00 00 00
00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-
Them bytes that look
On Tue, 3 Apr 2007 10:30:36 +0200,
Andi Kleen [EMAIL PROTECTED] wrote:
On Tuesday 03 April 2007 10:29:06 Christian Borntraeger wrote:
On Monday 02 April 2007 23:12, Andi Kleen wrote:
How would that work in the case where virtualized guests don't have a
visible PCI bus, and the
Paa Paa wrote:
I'm using Linux 2.6.20.4. I noticed that I get lower SATA hard drive
throughput with 2.6.20.4 than with 2.6.19. The reason was that 2.6.20
enables NCQ by defauly (queue_depth = 31/32 instead of 0/32). Transfer
rate was measured using hdparm -t:
With NCQ (queue_depth == 31):
On s390, it would be more than strangeness. There's no implementation
of PCI at all, someone would have to cook it up - and it wouldn't have
any use beyond those special devices. Since there isn't any bus type
that is available on *all* architectures, a generic virtual bus with
very simple
On Tue, 3 Apr 2007, Robert Marquardt wrote:
As this quirk is only needed once in the initialization method, we
could probably get rid of it and just put and explicit test for PID
and VID there (with apropriate comment). We can't afford wasting quirk
entries, as we are slowly running
[PATCH] kdump/kexec: calculate note size at compile time
Currently the size of the per-cpu region reserved to save crash
notes is set by the per-architecture value MAX_NOTE_BYTES. Which
in turn is currently set to 1024 on all supported architectures.
While testing ia64 I recently discovered that
On Tuesday 03 April 2007, H. Peter Anvin wrote:
However, one probably wants to think about what the heck one actually
means with virtualization in the absence of a lot of this stuff. PCI
is probably the closest thing we have to a lowest common denominator for
device detection.
I think
On Tue, 3 Apr 2007, Jarek Poplawski wrote:
Did you try with 8139cp instead of 8139too?
I forgot about that, thanks.
(Maybe even try some other card to narrow the problem?)
We're try to convince our hosting provider to replace the NIC with a
e1000.
You could also try to test without
On Mon, Apr 02, 2007 at 11:23:17PM -0600, Eric W. Biederman wrote:
Vivek Goyal [EMAIL PROTECTED] writes:
I guess at this point the easy case is that we modify /sbin/kexec to
support
it. And the other bootloaders can come be upgraded if the feature is
interesting enough.
On i386,
On Tue, 3 Apr 2007 11:41:49 +0200,
Arnd Bergmann [EMAIL PROTECTED] wrote:
On Tuesday 03 April 2007, H. Peter Anvin wrote:
However, one probably wants to think about what the heck one actually
means with virtualization in the absence of a lot of this stuff. PCI
is probably the closest
On Tuesday, 3 April 2007 09:37, Jiri Slaby wrote:
Rafael J. Wysocki napsal(a):
On Monday, 2 April 2007 10:24, Jiri Slaby wrote:
Rafael J. Wysocki napsal(a):
On Thursday, 29 March 2007 09:44, Jiri Slaby wrote:
swsusp: critical section:
swsusp: Need to copy 131380 pages
swsusp: Not
Hi,
Thanks for your comments.
I'm sorry for my late reply.
Bill Davidsen wrote:
Then, what do you think of the following idea?
(4) add `dirty_start_writeback_ratio' as percentage of memory,
at which a generator of dirty pages itself starts writeback
(that is, non-blocking ratio).
On Tue, 3 Apr 2007 11:26:52 +0200,
Andi Kleen [EMAIL PROTECTED] wrote:
On s390, it would be more than strangeness. There's no implementation
of PCI at all, someone would have to cook it up - and it wouldn't have
any use beyond those special devices. Since there isn't any bus type
that
This patchset is to avoid the problem that write(2) can be blocked for a
long time if a system has several disks with different speed and is
under heavy I/O pressure.
-Description of the problem:
While Dirty+Writeback pages get more than 40%(`dirty_ratio') of memory,
generators of dirty pages are
Hello,
I am doing some benchmarking on writes to the hdd from a simple
application (attached).
Im benchmarking the writes using the following
- write with O_DIRECT
- write with fadvise + O_SYNC
- write with fadvise + sync_file_range
Ive tested the writes in chunks of 4/8/16 KB and 1MB
The
This patch adds a sysctl variable `vm.dirty_start_writeback_ratio' to
enable users to adjust the writeback starting level of the dirty pages.
Signed-off-by: Tomoki Sekiyama [EMAIL PROTECTED]
---
Documentation/filesystems/proc.txt | 11 +--
Documentation/sysctl/vm.txt|3 ++-
On Tue, 2007-04-03 at 07:31 +0200, Mike Galbraith wrote:
On Tue, 2007-04-03 at 12:37 +1000, Con Kolivas wrote:
On Thursday 29 March 2007 15:50, Mike Galbraith wrote:
On Thu, 2007-03-29 at 09:44 +1000, Con Kolivas wrote:
+ * This contains a bitmap for each dynamic priority level with empty
Carlo Florendo wrote:
The kernel configure target make menuconfig requires ncurses. FWIW, it
could probably be better if the error message would indicate that that
ncurses is necessary for make menuconfig to run and that the user could
be prompted to install the package.
You could select
Hello!
Resetting the console, either by ANSI escape sequences or by the reset
utility,
will drop the console back to legacy (non-UTF-8) mode.
Yes, and as far as I understand the logic behind these escape sequences,
it's the intended behavior, not a bug.
The escape sequence for terminal
On Tuesday 03 April 2007, Cornelia Huck wrote:
I think that's true outside of s390, but a standardized virtual device
interface should be able to work there as well. Interestingly, the
s390 channel I/O also uses two 16 bit numbers to identify a device
(type and model), just like PCI or
Hi,
I implemented a struct reorganizer in pahole, one of the tools in
the dwarves suite I've been working on, it does several things to reduce
the size of structs:
1. demotes bitfields to a base type that is enough for the sum of the
members.
2. combines bitfields by moving members
3.
[please CC me on this thread]
Hi everyone,
My system has an nForce4 motherboard with an OHCI USB controller.
I'm using a USB Webcam with the gspca driver (from
http://mxhaard.free.fr/download.html), which has been working fine with the
latest kernels.
Today, I connected a USB Hub and the
On Sun, 01 Apr 2007, Jeremy Fitzhardinge wrote:
You can use ibm-acpi to properly track your thinkpad thermal sensors, load
it with the experimental=1 parameter, and look at what gets exported at
/proc/acpi/ibm/thermal.
Interesting. The first number corresponds with the ACPI THM0
On Tue, Apr 03, 2007 at 05:18:25PM +1000, Rusty Russell wrote:
On Mon, 2007-04-02 at 23:09 -0700, Andrew Morton wrote:
This is not about efficiency. When have I *ever* posted optimization
patches?
This is about clarity. We have a standard convention for
register/unregister. And they
From: Daniel P. Engel [EMAIL PROTECTED]
Add HID_QUIRK_HIDDEV for the Belkin Flip USB KVM to the hid-core
blacklist table. The Belkin Flip USB KVM provides for software
control of switching via a HID class interface. It overloads
three HID LED usages, two of which aren't mapped in the ev_dev input
Hi!
block/genhd.c | 54
++
include/linux/genhd.h |1
init/do_mounts.c |7 +-
3 files changed, 61 insertions(+), 1 deletion(-)
Index: linux-2.6.21-rc5/block/genhd.c
Hi!
Allow for the palette to be exposed and changed via sysfs. A call to
/usr/bin/reset will slurp the new definitions in for the current
console.
I like this. The escape sequences to change the palette does not stay
permanently.
As much as you like it, there is a slight problem with
On 04/02, Gautham R Shenoy wrote:
Clean up workqueue.c from the perspective of freezer-based cpu-hotplug.
This patch
I'll study these patches later, a couple of comments after the quick reading.
This means that all non-singlethreaded workqueues *have* to
be frozen to avoid any races.
On Mon, Apr 02, 2007 at 08:56:07PM +0200, Ingo Molnar wrote:
ok. But the only real problem would be for_each_online_cpu() loops that
might sleep, correct?
I would shy from saying that that's the only problem. It could also be
for_each_cpu_mask(some_mask)
Currently the i386 architecture checks the family for mce capability and this
removes that and uses the CPUID information. Tested on a K8 revE and a
family10h processor.
-Joachim
This eliminates checking of a set AMD procesor family if mce is
allowed and relies on the information being in
On Mon, 2 Apr 2007, Andrew Morton wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc5/2.6.21-rc5-mm4/
[proper CCs added]
On boot (e1000 compiled as module)
BUG: unable to handle kernel paging request at virtual address
printing eip:
*pde =
[EMAIL PROTECTED] wrote:
Anyway, what's annoying is that I can't figure out how to bring the
drive back on line without resetting the box. It's in a hot-swap enclosure,
but power cycling the drive doesn't seem to help. I thought libata hotplug
was working? (SiI3132 card, using the sil24
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Anyway, what's annoying is that I can't figure out how to bring the
drive back on line without resetting the box. It's in a hot-swap enclosure,
but power cycling the drive doesn't seem to help. I thought libata hotplug
was working? (SiI3132
Hello all,
I have idea to include to the user the following new per-process
(thread) performance statistics:
* Involuntary Context Switches
* Voluntary Context Switches
* Number of system calls
What do you think about it? Patch is bellow.
Best regards,
Max Uvarov.
Description:
rt10 shows a big improvement over rt8
##
etupThruput CPU%
Nvidia
2.6.21-rc5-rt8 938 65%
netperf @51
hardirq @50
softirq @50
Nvidia
2.6.21-rc5-rt10 938 32%
netperf @51
On Mon, Apr 02, 2007 at 02:10:29PM +0200, Andi Kleen wrote:
On Monday 02 April 2007 13:38, Alexey Dobriyan wrote:
They will be used by cpuid driver and powernow-k8 cpufreq driver.
With these changes powernow-k8 driver could run correctly on OpenVZ kernels
with virtual cpus enabled
On Tue, 3 Apr 2007 14:15:37 +0200,
Arnd Bergmann [EMAIL PROTECTED] wrote:
Right, but an interesting point is the question what to do when running
another operating system as a guest under Linux, e.g. with kvm.
Ideally, you'd want to use the same interface to announce the presence
of the
Both powernow-k8 and cpuid attempt to schedule
to the target CPU so they should already run there. But it is some other
CPU,
but when they ask your _on_cpu() functions they suddenly get a real CPU?
Where is the difference between these levels of virtualness?
*_on_cpu functions do
On Tue, Apr 03, 2007 at 03:47:29PM +0400, Oleg Nesterov wrote:
I still think that wait_to_die + bind_cpu is unneeded complication.
Why can't we do the following:
static int worker_thread(void *__cwq)
{
...
for (;;) {
Move generic skbuff stuff from XFRM code to generic code so that AF_RXRPC can
use it too.
The kdoc comments I've attached to the functions needs to be checked by whoever
wrote them as I had to make some guesses about the workings of these functions.
Signed-Off-By: David Howells [EMAIL PROTECTED]
Export the keyring key type definition and document its availability.
Add alternative types into the key's type_data union to make it more useful.
Not all users necessarily want to use it as a list_head (AF_RXRPC doesn't, for
example), so make it clear that it can be used in other ways.
Export try_to_del_timer_sync() for use by the RxRPC module.
Add a try_to_cancel_delayed_work() so that it is possible to merely attempt to
cancel a delayed work timer.
Signed-Off-By: David Howells [EMAIL PROTECTED]
---
include/linux/workqueue.h | 21 +
kernel/timer.c
Add an interface to the AF_RXRPC module so that the AFS filesystem module can
more easily make use of the services available. AFS still opens a socket but
then uses the action functions in lieu of sendmsg() and registers an intercept
functions to grab messages before they're queued on the socket
The first of these patches together provide secure client-side RxRPC
connectivity as a Linux kernel socket family. Only the RxRPC transport/session
side is supplied - the presentation side (marshalling the data) is left to the
client. Copies of the patches can be found here:
On Tuesday 03 April 2007, Cornelia Huck wrote:
On Tue, 3 Apr 2007 14:15:37 +0200, Arnd Bergmann [EMAIL PROTECTED] wrote:
That's OK for a virtualized architecture where the base architecture
already supports PCI. But a traditional s390 OS would be as unhappy
with a PCI device as with a device
Some BIOSes may modify fixed-range MTRRs in SMM, e.g. when they
transition the system into ACPI mode, which is entered thru an SMI,
triggered by Linux in acpi_enable().
SMIs which cause that Linux is interrupted and BIOS code is
executed (which may change e.g. fixed-range MTRRs) in SMM may
be
If our copy of the MTRRs of the BSP has RdMem or WrMem set and
we are running on an AMD64/K8 system, the boot CPU must have had
MtrrFixDramEn and MtrrFixDramModEn set (otherwise our RDMSR would
have copied these bits cleared), so we set them on this CPU as well.
This allows us to keep the
On Mon, Apr 02, 2007 at 12:02:35PM -0600, Eric W. Biederman wrote:
If we loose directories, then we don't have a way to manage the
task-group it represents thr' the filesystem interface, so I consider
that bad. As we agree, this will not be an issue if initrd
mounts the ns hierarchy
On Mon, Mar 26, 2007 at 11:35:42PM -0800, [EMAIL PROTECTED] wrote:
The patch titled
add file position info to proc
has been added to the -mm tree. Its filename is
add-file-position-info-to-proc.patch
I tried to stress-test it with the following program and script and
lockdep barfs
Hi,
With at least 3 of the following 4 patches, s2ram and s2disk are
fixed on at least the Acer Ferrari 1000 notebooks and at least
s2disk on the Acer Ferrari 5000 notebooks.
The Acer Ferrari 1000 is a 12 Turion 64 X2 notebook with only 1.7 kg weight
while the Ferrari 5000 is a 14 AMD Turion
This patch implements mtrr_save_fixed_ranges() which can be called
from anywhere anytime to retrieve the fixed-range MTRRs from the
current CPU and saves these MTRR values to the MTRR state struct.
This function calls get_fixed_ranges(), passing mtrr_state.fixed_ranges
which is the element of the
While I haven't found this as cause of the MTRR suspend issue on the
Ferraris, AMD and Intel x86 CPU manuals state that it is the responsibility
of system software to initialize and maintain MTRR consistency across
all processors in Multi-Processing Environments:
Quote from page 188 of the AMD64
On Mon, Apr 02, 2007 at 08:16:12AM +0200, Ingo Molnar wrote:
i'm wondering about how TASK_UNINTERRUPTIBLE tasks are handled by the
freezer: are they assumed frozen immediately, or do we wait until they
notice their PF_FREEZING and go into try_to_freeze()? I'd expect
TASK_UNINTERRUPTIBLE to
On 04/03/2007 08:57 AM, Pekka J Enberg wrote:
[ re-including linux-kernel ]
Does this change the dd case?
diff --git a/drivers/cdrom/mcdx.c b/drivers/cdrom/mcdx.c
index f574962..6c613d0 100644
--- a/drivers/cdrom/mcdx.c
+++ b/drivers/cdrom/mcdx.c
@@ -1248,6 +1248,7 @@ #endif
Christian Kujau wrote:
Len et al., do you even suggest to use ACPI on a server system at all? I
myself always thought of ACPI being evil and to avoid when possible
(thus switching it off completely on a serversystem).
These days I think it's usually best to have ACPI on with current
systems.
On 04/03/2007 08:57 AM, Pekka J Enberg wrote:
Does this change the dd case?
diff --git a/drivers/cdrom/mcdx.c b/drivers/cdrom/mcdx.c
index f574962..6c613d0 100644
--- a/drivers/cdrom/mcdx.c
+++ b/drivers/cdrom/mcdx.c
@@ -1248,6 +1248,7 @@ #endif
disk-private_data = stuffp;
Michael Bueker wrote:
[please CC me on this thread]
Hi everyone,
My system has an nForce4 motherboard with an OHCI USB controller.
I'm using a USB Webcam with the gspca driver (from
http://mxhaard.free.fr/download.html), which has been working fine with the
latest kernels.
Today, I connected
Michael Bueker wrote :
I'm using a USB Webcam with the gspca driver (from
http://mxhaard.free.fr/download.html), which has been working fine with the
latest kernels.
...
Now, I'm writing to this list because one of the followups to that post
Hi,
A new version of the per BDI dirty page throttle patches.
This is against 2.6.21-rc5-mm4 with:
per-backing_dev-dirty-and-writeback-page-accounting.patch
reverted.
These patches should solve several problem we current have in this area,
namely:
- mutual interference starvation (for any
Count per BDI writeback pages.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
include/linux/backing-dev.h |1 +
mm/page-writeback.c |8 ++--
2 files changed, 7 insertions(+), 2 deletions(-)
Index: linux-2.6/mm/page-writeback.c
Count per BDI unstable pages.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
fs/nfs/write.c |4
include/linux/backing-dev.h |1 +
2 files changed, 5 insertions(+)
Index: linux-2.6/fs/nfs/write.c
===
Count per BDI dirty pages.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
fs/buffer.c |1 +
include/linux/backing-dev.h |1 +
mm/page-writeback.c |2 ++
mm/truncate.c |1 +
4 files changed, 5 insertions(+)
Index: linux-2.6/fs/buffer.c
Provide scalable per backing_dev_info statistics counters modeled on the ZVC
code.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
block/ll_rw_blk.c |1
drivers/block/rd.c |2
drivers/char/mem.c |2
fs/char_dev.c |1
Scale writeback cache per backing device, proportional to its writeout speed.
akpm sayeth:
Which problem are we trying to solve here? afaik our two uppermost
problems are:
a) Heavy write to queue A causes light writer to queue B to blok for a long
time in balance_dirty_pages(). Even if
Expose the per BDI stats in /sys/block/dev/queue/*
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
block/ll_rw_blk.c | 81
mm/page-writeback.c |2 -
2 files changed, 82 insertions(+), 1 deletion(-)
Index:
On Tue, Apr 03, 2007 at 03:42:50PM +0200, Andi Kleen wrote:
Both powernow-k8 and cpuid attempt to schedule
to the target CPU so they should already run there. But it is some other
CPU,
but when they ask your _on_cpu() functions they suddenly get a real CPU?
Where is the difference
1 - 100 of 934 matches
Mail list logo
