18 Nis 2007 Çar tarihinde, Christoph Pfister şunları yazmıştı:
Okay - so here are some results (it's strange that gdb goes nuts
inside the xine_play call). I have three bts (seems to be fairly easy
to reproduce that behaviour over here): Twice while playing an audio
cd and once while
On Wed, Apr 18, 2007 at 12:55:25AM -0500, Matt Mackall wrote:
Why are processes special? Should user A be able to get more CPU time
for his job than user B by splitting it into N parallel jobs? Should
we be fair per process, per user, per thread group, per session, per
controlling terminal?
On Wed, 2007-04-18 at 07:38 -0500, Florin Iucha wrote:
On Tue, Apr 17, 2007 at 10:37:38PM -0700, Andrew Morton wrote:
Florin, can we please see /proc/meminfo as well?
http://iucha.net/nfs/21-rc7-nfs2/meminfo
Also the result of `echo m /proc/sysrq-trigger'
On Wed, Apr 18 2007, Jens Axboe wrote:
I had something similar for generic_unplug_request() as well, but didn't
see/hear any reports of it being tried out. Here's a complete debugging
patch for this and other potential dangers.
Which had a bug (do the check _after_ deleting from the rbtree,
2007/4/18, Christoph Pfister [EMAIL PROTECTED]:
[ Sorry for accidentally dropping CCs ]
2007/4/18, Christoph Pfister [EMAIL PROTECTED]:
2007/4/18, Ingo Molnar [EMAIL PROTECTED]:
* Christoph Pfister [EMAIL PROTECTED] wrote:
Or I could try playing around a bit with your patchset and
Jens Axboe wrote:
I had something similar for generic_unplug_request() as well, but didn't
see/hear any reports of it being tried out. Here's a complete debugging
patch for this and other potential dangers.
I had a clean 2.6.21-rc7 that I forgot to change the default sched on take down my
On Wed, Apr 18 2007, Brad Campbell wrote:
Jens Axboe wrote:
I had something similar for generic_unplug_request() as well, but didn't
see/hear any reports of it being tried out. Here's a complete debugging
patch for this and other potential dangers.
I had a clean 2.6.21-rc7 that I forgot
18 Nis 2007 Çar tarihinde, Christoph Pfister şunları yazmıştı:
Replacing the sched_yield in demux.c with an usleep(10) stopped those
seeking hangs here (at least I was able to pull the slider back and
forth during 2 mins without trouble compared to the few secs I need
earlier to get a hang).
Hi,
While running some tests on 2.6.20-rt8 with DEBUG_PREEMPT on, I hit the
following BUG:
BUG: using smp_processor_id() in preemptible [] code: nfsd/2852
caller is drain_array+0x25/0x132
Call Trace:
[8026d828] dump_trace+0xbd/0x3d8
[8026db87] show_trace+0x44/0x6d
--- Joshua Brindle [EMAIL PROTECTED] wrote:
Biba and BLP are only incompatible if they are using the same label, if
each object has a confidentiality and integrity label they work fine
together
Joshua is correct here, although the original Biba observation was
that flipping BLP upside
On Wed, 18 Apr 2007, David Lang wrote:
SELinux is designed to be able to make the box safe against root, AA is
designed to let the admin harden exposed apps without having to think about
the other things on the system.
This is not correct.
SELinux was designed as an access control framework
Alan Cox wrote:
Thought about that and querying power state before doing shutdown
sequence but things get somewhat ugly because shutdown sequence is
driven from sd-shutdown(). We'll have to snoop both sync and shutdown
commands and check whether the system is shutting down. Also, I felt
On Wed, Apr 18, 2007 at 09:15:31AM -0400, Trond Myklebust wrote:
There is only one request on the 'pending' queue. That would usually
indicate that the connection to the server is down. Can you check using
netstat -t whether or not there is a connection in the 'ESTABLISHED'
state to the
On Tue, 17 Apr 2007, Alan Cox wrote:
I'm not sure if AppArmor can be made good security for the general case,
but it is a model that works in the limited http environment
(eg .htaccess) and is something people can play with and hack on and may
be possible to configure to be very secure.
On Sun, Apr 15, 2007 at 11:26:05PM +0800, [EMAIL PROTECTED] wrote:
(Adding a few more people to the cc'list)
sound/core/pcm_native.c | 10 ++
sound/core/sgbuf.c |9 +
2 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/sound/core/pcm_native.c
Running benchmark tests (FFSB) on an ext4 filesystem, I noticed a
performance degradation (about 15-20 percent) in sequential write tests
between 2.6.19-rc6 and 2.6.21-rc4 kernels.
I ran the same tests on ext3 and XFS filesystems and I saw the same
performance difference between the two
On Wed, 2007-04-18 at 11:11 +0200, Miklos Szeredi wrote:
I've tried to make this unprivileged mount thing as simple as
possible, and no simpler. If we can make it even simpler, all the
better.
We are certainly much more complex then the code in plan9 (just
read through it) so I
I've tried to make this unprivileged mount thing as simple as
possible, and no simpler. If we can make it even simpler, all the
better.
We are certainly much more complex then the code in plan9 (just
read through it) so I think we have room for improvement.
Just for
On Wed, April 18, 2007 14:15, Joshua Brindle wrote:
Having said that, I feel a path based solution could have great
potential
if it could be used in conjunction with the object capability model,
that
I would consider a simple and practical alternative integrity model that
does not require
On 4/18/07, John Sigler [EMAIL PROTECTED] wrote:
Andi Kleen wrote:
There are usually chipset specific bits that can be set to disable
SMMs. See the datasheet if you can get them. Unfortunately most
chipset vendors don't give out data sheets easily.
I managed to find the south bridge data
On Wed, 2007-04-18 at 08:42 -0500, Florin Iucha wrote:
On Wed, Apr 18, 2007 at 09:15:31AM -0400, Trond Myklebust wrote:
There is only one request on the 'pending' queue. That would usually
indicate that the connection to the server is down. Can you check using
netstat -t whether or not
On Wed, Apr 18, 2007 at 08:42:25AM -0500, Florin Iucha wrote:
On Wed, Apr 18, 2007 at 09:15:31AM -0400, Trond Myklebust wrote:
The netstat outputs are stable (not changed in 5 minutes):
http://iucha.net/nfs/21-rc7-nfs3/netstat-server :
tcp1 0 hermes.iucha.org:nfs
On Wed, Apr 18, 2007 at 10:11:46AM -0400, Trond Myklebust wrote:
On Wed, 2007-04-18 at 08:42 -0500, Florin Iucha wrote:
Could the port in CLOSE_WAIT state be the culprit? (FWIW
the server has been up for 38 days and subjected to
this nfs test quite a bit without showing any stress).
The
Hello
On Wednesday 18 April 2007 12:52, ReiserFS Developers Mailing List wrote:
*Forwarded Conversation*
Subject: *[2.6.20.4] BUG: dentry xattrs still in use in
shrink_dcache_for_umount() with reiserfs*
* From: Andrea Righi* [EMAIL PROTECTED] Reply-To:
[EMAIL
On Wed, 2007-04-18 at 09:17 -0500, Florin Iucha wrote:
On Wed, Apr 18, 2007 at 10:11:46AM -0400, Trond Myklebust wrote:
On Wed, 2007-04-18 at 08:42 -0500, Florin Iucha wrote:
Could the port in CLOSE_WAIT state be the culprit? (FWIW
the server has been up for 38 days and subjected to
vaddr = runtime-dma_area + offset;
+#if defined(__mips__) defined(CONFIG_DMA_NONCOHERENT)
Please use CONFIG_MIPS instead of __mips__ in #if / #ifdefs.
The question if #ifdefing is the right approach to solve this problem is
something else but I think no,
I would
Madhusudhan c wrote:
Kyung-ju Hyun from samsung had submitted a patch for MMCPlus support
long back, which had the bus testing procedure implemented and it
works fine. I am able to write and read the data pattern back
successfuly with his patch. I am not sure why his patch was not
Alan Cox wrote:
If you see a synchronize cache succeed and you then see the drive
shutdown succeed then you know that a sync cache can be faked as ok
safely. Any other command in between or after and it doesn't get faked
This seems pretty easy to deal with at command issue.
Yup. It could be
James Morris wrote:
On Tue, 17 Apr 2007, Alan Cox wrote:
I'm not sure if AppArmor can be made good security for the general case,
but it is a model that works in the limited http environment
(eg .htaccess) and is something people can play with and hack on and may
be possible to configure to be
Mark Lord wrote:
Alan Cox wrote:
If you see a synchronize cache succeed and you then see the drive
shutdown succeed then you know that a sync cache can be faked as ok
safely. Any other command in between or after and it doesn't get faked
This seems pretty easy to deal with at command issue.
On Wed, 2007-04-18 at 16:03 +0200, Miklos Szeredi wrote:
Don't forget that almost all mount flags are per-superblock. How are you
planning on dealing with the case that one user mounts a filesystem
read-only, while another is trying to mount the same one read-write?
Yeah, I forgot, the
Max Kellermann wrote:
Yet another hard drive which doesn't seem to get NCQ right.
ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl
0x1501000 status 0x400 next cpb count 0xB next cpb idx 0x0
[...]
ata1: timeout waiting for ADMA IDLE, stat=0x400
ata1: timeout waiting for ADMA
Andrew Shewmaker wrote:
John Sigler wrote:
Andi Kleen wrote:
There are usually chipset specific bits that can be set to disable
SMMs. See the datasheet if you can get them. Unfortunately most
chipset vendors don't give out data sheets easily.
I managed to find the south bridge data sheet.
Is there any knob/option to prevent libata
probing non-existent channels ?
Specifically how can I stop the kernel probing
the second SATA? -
4ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
7libata version 2.00 loaded.
7ata_piix :00:1f.2: version 2.00ac7
6ata_piix :00:1f.2: MAP [ P0 P2 P1 P3 ]
6GSI
On Wed, 18 Apr 2007 21:06:41 +0900
Keiichi KII [EMAIL PROTECTED] wrote:
From: Keiichi KII [EMAIL PROTECTED]
This patch contains the following changes for supporting multiple logging
agents.
1. extend netconsole to multiple netpolls
To send kernel messages to multiple logging agents,
On Wed, 18 Apr 2007, Matt Mackall wrote:
Why is X special? Because it does work on behalf of other processes?
Lots of things do this. Perhaps a scheduler should focus entirely on
the implicit and directed wakeup matrix and optimizing that
instead[1].
I 100% agree - the perfect scheduler
On Wed, 18 Apr 2007, Tejun Heo wrote:
Hello, all.
Agreed with the problem but I'm not very enthusiastic for adding
kobj-owner. How about the following? exit() routines will have to
do device_unregister_wait() instead of device_unregister(). On return
from it, it's guaranteed that all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir V. Saveliev wrote:
Hello
On Wednesday 18 April 2007 12:52, ReiserFS Developers Mailing List wrote:
*Forwarded Conversation*
Subject: *[2.6.20.4] BUG: dentry xattrs still in use in
shrink_dcache_for_umount() with reiserfs*
On Wed, Apr 18, 2007 at 10:26:29AM -0400, Trond Myklebust wrote:
That doesn't really change my agrument though. _If_ the flag is per
mount, then it makes sense to be able to change it on a master and not
on a slave. If mount flags are propagated, this is not possible.
Read-only isn't
On Wed, 18 Apr 2007 03:41:10 +0900,
Tejun Heo [EMAIL PROTECTED] wrote:
patch
OK, I hit a bit on the code. Once I saved a reference to the completion
in kobject_cleanup, it seemed to survive a load/unload testloop for a
module registering a device. However, I still dislike this list of
waiters
+ if (dev-needs_flush ata_try_flush_cache(dev)) {
return ata_scsi_flush_xlat;
+ dev-needs_flush = 0;
Works better if you swap the dev- and return lines
Alan
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
Don't forget that almost all mount flags are per-superblock. How are you
planning on dealing with the case that one user mounts a filesystem
read-only, while another is trying to mount the same one read-write?
Yeah, I forgot, the per-mount read-only patches are not yet in.
That
according to http://lwn.net/Articles/167034/ binary semaphores (which
aren't given in interrupt context or locked/unlocked in different
process contexts) should be converted to the new mutex API.
this patch converts the semaphore used by the Smart Battery System
ACPI interface driver to a mutex.
* Christoph Pfister [EMAIL PROTECTED] wrote:
Replacing the sched_yield in demux.c with an usleep(10) stopped those
seeking hangs here (at least I was able to pull the slider back and
forth during 2 mins without trouble compared to the few secs I need
earlier to get a hang).
great -
Alan Cox wrote:
+ if (dev-needs_flush ata_try_flush_cache(dev)) {
return ata_scsi_flush_xlat;
+ dev-needs_flush = 0;
Works better if you swap the dev- and return lines
Heh, yeah, I noticed that!
Here it is, *tested* now, with
* Ankita Garg [EMAIL PROTECTED] wrote:
While running some tests on 2.6.20-rt8 with DEBUG_PREEMPT on, I hit
the following BUG:
This patch fixes the above issue which arises due to the call to
smp_processor_id in drain_array() from mm/slab.c. smp_processor_id()
invocation is redundant
On Wed, 18 Apr 2007, Rusty Russell wrote:
Hi Alan,
Your assertion is correct. I haven't studied the driver core, so I
might be off-base here, but you'll note that if the module references
the core kmalloc'ed object rather than the other way around it can be
done safely. The core
On Wed, 18 Apr 2007 10:53:55 -0400 (EDT),
Alan Stern [EMAIL PROTECTED] wrote:
Many drivers, especially those for hot-pluggable buses, register and
unregister devices dynamically. These events can occur in time-critical
situations, where the driver cannot afford to wait for all the references
Mark Lord wrote:
Alan Cox wrote:
+if (dev-needs_flush ata_try_flush_cache(dev)) {
return ata_scsi_flush_xlat;
+dev-needs_flush = 0;
Works better if you swap the dev- and return lines
Heh, yeah, I noticed that!
Here it is, *tested* now, with another
Hello,
Alan Stern wrote:
On Wed, 18 Apr 2007, Tejun Heo wrote:
Hello, all.
Agreed with the problem but I'm not very enthusiastic for adding
kobj-owner. How about the following? exit() routines will have to
do device_unregister_wait() instead of device_unregister(). On return
from it,
Aubrey Li [EMAIL PROTECTED] wrote:
Here, in the attachment I wrote a small test app. Please correct if
there is anything wrong, and feel free to improve it.
Okay... I have that working... probably. I don't know what output it's
supposed to produce, but I see this:
#
On Wed, Apr 18, 2007 at 07:48:21AM -0700, Linus Torvalds wrote:
And fairness by euid is probably a hell of a lot easier to do than
trying to figure out the wakeup matrix.
For the record, you actually don't need to track a whole NxN matrix
(or do the implied O(n**3) matrix inversion!) to get to
Tejun Heo wrote:
Incidentally, Tejun, I'm all in favor of a immediate-detach driver model
approach. Unfortunately it's impossible to realize fully, although we
could come much closer than we are now.
Here's an example where immediate-detach cannot be implemented. A driver
binds to a
* S.Çağlar Onur [EMAIL PROTECTED] wrote:
- schedule();
+ msleep(1);
which Ingo sends me to try also has the same effect on me. I cannot
reproduce hangs anymore with that patch applied top of CFS while one
console checks out SVN repos and other one compiles a small test
With the move to initramfs and heavily modular configs, which include
loading storage drivers from early userspace, it's becoming harder
to provide users with a way of overriding module parameters at boot.
Currently, users would have to break into the initramfs, edit the
modprobe options, and
On Tue, 17 Apr 2007 12:49:07 +0200 Borislav Petkov wrote:
On Sun, Apr 15, 2007 at 09:10:50AM +0200, Borislav Petkov wrote:
On Sat, Apr 14, 2007 at 09:13:41AM -0700, Randy Dunlap wrote:
On Fri, 13 Apr 2007 11:14:22 +0200 Borislav Petkov wrote:
This patch shuts warnings of the sort:
Cornelia Huck wrote:
On Wed, 18 Apr 2007 03:41:10 +0900,
Tejun Heo [EMAIL PROTECTED] wrote:
patch
OK, I hit a bit on the code. Once I saved a reference to the completion
in kobject_cleanup, it seemed to survive a load/unload testloop for a
module registering a device. However, I still
On Wed, Apr 18, 2007 at 05:48:11PM +0200, Ingo Molnar wrote:
static void requeue_task_fair(struct rq *rq, struct task_struct *p)
{
dequeue_task_fair(rq, p);
p-on_rq = 0;
- enqueue_task_fair(rq, p);
+ /*
+ * Temporarily insert at the last position of the tree:
+
On Thu, 19 Apr 2007, Tejun Heo wrote:
The goal of immediate-disconnect is to remove such lingering reference
counts so that device_unregister() or driver detach puts the last
reference count.
Yes, I understand. If you had immediate-disconnect then you wouldn't need
device_unregister_wait().
Mates,
First post and I am having heck building the vanilla 2.6.20.7 kernel on
Suse 10.0. Basically I put 2.6.20.7 in /usr/src, then I did
cd linux
(read Documentation/Changes Current Minimal Requirements)
zcat /proc/config.gz .config
make oldconfig
make
make modules
make modules_install
* William Lee Irwin III [EMAIL PROTECTED] wrote:
At this point you might as well call the requeue operation something
having to do with yield. [...]
agreed - i've just done a requeue_task - yield_task rename in my tree.
(patch below)
[...] I also suspect what goes on during the timer tick
Alan Cox wrote:
The basic reason for all this is to eventually allow the low-level
serial drivers to function without a uart_info structure being
allocated. This will allow the serial console, debuggers like kgdb,
and the IPMI serial driver to use one interface to the uart code and
On Wed, 18 Apr 2007 17:21:53 +0900 Kenji Kaneshige [EMAIL PROTECTED] wrote:
I'd imagine that other serial drivers might get upset having their
-get_mcrtl() called prior to being opened. Perhaps we should be fixing
this in uart_read_proc()?
I looked at other serial drivers and I could
Hello,
Alan Stern wrote:
On Thu, 19 Apr 2007, Tejun Heo wrote:
The goal of immediate-disconnect is to remove such lingering reference
counts so that device_unregister() or driver detach puts the last
reference count.
Yes, I understand. If you had immediate-disconnect then you wouldn't
Hi Ingo and all,
On Friday 13 April 2007, Ingo Molnar wrote:
as usual, any sort of feedback, bugreports, fixes and suggestions are
more than welcome,
I just gave CFS a try on my system. From a user's point of view it looks good
so far. Thanks for your work.
However I found a problem: When
On Wed, 2007-04-18 at 10:19 +0200, Peter Zijlstra wrote:
On Tue, 2007-04-17 at 21:19 -0400, Trond Myklebust wrote:
I've split the issues introduced by the 2.6.21-rcX write code up into 4
subproblems.
The first patch is just a cleanup in order to ease review.
Patch number 2 ensures
On 4/18/07, Tejun Heo [EMAIL PROTECTED] wrote:
Hello,
Alan Stern wrote:
On Wed, 18 Apr 2007, Tejun Heo wrote:
Hello, all.
Agreed with the problem but I'm not very enthusiastic for adding
kobj-owner. How about the following? exit() routines will have to
do device_unregister_wait()
* Christian Hesse [EMAIL PROTECTED] wrote:
Hi Ingo and all,
On Friday 13 April 2007, Ingo Molnar wrote:
as usual, any sort of feedback, bugreports, fixes and suggestions are
more than welcome,
I just gave CFS a try on my system. From a user's point of view it
looks good so far.
SPIN_LOCK_UNLOCKED cleanup,use __SPIN_LOCK_UNLOCKED instead
Signed-off-by: Milind Arun Choudhary [EMAIL PROTECTED]
---
amiga/amiints.c |2 +-
amiga/cia.c |4 ++--
apollo/dn_ints.c |2 +-
atari/ataints.c |2 +-
kernel/ints.c|4 ++--
mac/macints.c|2 +-
On Wed, 2007-04-18 at 11:55 -0400, Kyle McMartin wrote:
With the move to initramfs and heavily modular configs, which include
loading storage drivers from early userspace, it's becoming harder
to provide users with a way of overriding module parameters at boot.
Currently, users would have to
On Wednesday, 18 April 2007 11:42, Gautham R Shenoy wrote:
Hi,
The patch looks good to me.
On Mon, Apr 16, 2007 at 11:27:58PM +0200, Rafael J. Wysocki wrote:
---
Documentation/cpu-hotplug.txt |9 +++--
arch/i386/kernel/cpu/intel_cacheinfo.c|2 ++
अभिजित भोपटकर (Abhijit Bhopatkar) wrote:
The mm structures of interactive tasks are marked and
the pages belonging to them are never shifted to inactive
list in lru algorithm. Thus keeping interactive tasks in
memory as long as possible.
The interactivity is already determined by schedular so
we
Mark Lord wrote:
Alan Cox wrote:
+ if (dev-needs_flush ata_try_flush_cache(dev)) {
return ata_scsi_flush_xlat;
+ dev-needs_flush = 0;
Works better if you swap the dev- and return lines
Heh, yeah, I noticed that!
Tejun Heo wrote:
Mark Lord wrote:
..
It would be nice if somebody who can hear the pop would also test this,
as it will confirm that this is a complete fix for the problem.
You'll probably be able to here the pop on sleep-to-disk.
My pop drives are busy elsewhere right now.
The system I
On Mon, Apr 16, 2007 at 01:08:57PM -0700, Andrew Vasquez wrote:
Sorry, but in a SATA/SCSI environment that may be true, but in the
case of FC that expectation is unrealistic. There are thousands of FC
installations where there are several thousand endpoints (including
initiators and targets)
On Fri, 13 Apr 2007 11:29:43 +0200 Borislav Petkov wrote:
Sorry for the improper whitespaces, here's a correct version.
Signed-off-by: Borislav Petkov [EMAIL PROTECTED]
Index: 21-rc6/scripts/kernel-doc
===
---
On Tue, Apr 17, 2007 at 11:28:07AM -0700, Seokmann Ju wrote:
Hello David,
On Mon 4/16/2007 10:02 PM, David Miller wrote:
I'm in transit for a redeye to NY so I won't be able to modify the
patch, If you would be amenable to the above, Seokmann, could you
rework the patch?
Thanks
Miklos Szeredi [EMAIL PROTECTED] writes:
I've tried to make this unprivileged mount thing as simple as
possible, and no simpler. If we can make it even simpler, all the
better.
We are certainly much more complex then the code in plan9 (just
read through it) so I think we have room for
Mark Lord wrote:
With the patch applied, I don't see *any* new activity in those S.M.A.R.T.
attributes over multiple hibernates (Linux suspend-to-disk).
Scratch that -- operator failure. ;)
The patch makes no difference over hibernates in the SMART logs.
It's still logging extra
On Wed, 18 Apr 2007, Matt Mackall wrote:
On Wed, Apr 18, 2007 at 07:48:21AM -0700, Linus Torvalds wrote:
And fairness by euid is probably a hell of a lot easier to do than
trying to figure out the wakeup matrix.
For the record, you actually don't need to track a whole NxN matrix
(or
On Mon, Apr 16, 2007 at 10:18:45PM +0200, Tomasz K?oczko wrote:
Of cources it can be true in most cases (probably for some more advanced
RAID controlers). Few weeks ago I perform some basic test on Dell 2950
with 8x73GB SAS disk .. just as for kill time (waiting for access to some
bigger
On Wed, 18 Apr 2007, Christoph Hellwig wrote:
I don't think a module option is a good idea at this point. The problem
is you broke some so far perfectly working setups, which is not okay.
The only first step can be printing a really big warning. After this
has been in for a while (at lest
Lennart Sorensen wrote:
On Mon, Apr 16, 2007 at 10:18:45PM +0200, Tomasz K?oczko wrote:
Of cources it can be true in most cases (probably for some more advanced
RAID controlers). Few weeks ago I perform some basic test on Dell 2950
with 8x73GB SAS disk .. just as for kill time (waiting for
On Sat, Apr 14, 2007 at 07:28:07PM +0200, Jean Delvare wrote:
Otherwise it looks OK to me, I take the patch. If others have comments
or objections, just speak up and submit incremental patches as needed.
Now I would like to see platform code actually using this.
Any idea how similar this new
Mark Lord wrote:
Mark Lord wrote:
With the patch applied, I don't see *any* new activity in those S.M.A.R.T.
attributes over multiple hibernates (Linux suspend-to-disk).
Scratch that -- operator failure. ;)
The patch makes no difference over hibernates in the SMART logs.
It's still
Mark Lord wrote:
Mark Lord wrote:
With the patch applied, I don't see *any* new activity in those
S.M.A.R.T.
attributes over multiple hibernates (Linux suspend-to-disk).
Scratch that -- operator failure. ;)
The patch makes no difference over hibernates in the SMART logs.
It's still
* Linus Torvalds [EMAIL PROTECTED] wrote:
The fact is:
- fairness is *not* about giving everybody the same amount of CPU
time (scaled by some niceness level or not). Anybody who thinks
that is fair is just being silly and hasn't thought it through.
yeah, very much so.
But note
this is the third release of the CFS patchset (against v2.6.21-rc7), and
can be downloaded from:
http://redhat.com/~mingo/cfs-scheduler/
this is a pure fix reported regressions release so there's much less
churn:
5 files changed, 71 insertions(+), 29 deletions(-)
(the added lines are
* Ingo Molnar [EMAIL PROTECTED] wrote:
In that sense 'fairness' is not global (and in fact it is almost
_never_ a global property, as X runs under root uid [*]), it is only
the most lowlevel scheduling machinery that can then be built upon.
[...]
perhaps a more fitting term would be
All the exports in utrace are totally unused, and not really something
I'd want modules to use anyway :)
Signed-off-by: Christoph Hellwig [EMAIL PROTECTED]
Index: linux-2.6/arch/i386/kernel/ptrace.c
===
---
On Wed, Apr 18, 2007 at 10:22:59AM -0700, Linus Torvalds wrote:
So I claim that anything that cannot be fair by user ID is actually really
REALLY unfair. I think it's absolutely humongously STUPID to call
something the Completely Fair Scheduler, and then just be fair on a
thread level.
Currently generic code calls into tracehook_* which then alls into
utrace_* to do the actual work. With utrace as the new singing dancing
framework there's little point in that, and readability would be greatly
improved by getting rid of this. The few places where tracehook_*
was more than a
I've tried to make this unprivileged mount thing as simple as
possible, and no simpler. If we can make it even simpler, all the
better.
We are certainly much more complex then the code in plan9 (just
read through it) so I think we have room for improvement.
Just for reference
Robert P. J. Day wrote:
On Tue, 17 Apr 2007, Bill Davidsen wrote:
Rafael J. Wysocki wrote:
[appropriate CCs added]
On Friday, 13 April 2007 02:33, Robert P. J. Day wrote:
just something i threw together, not in final form, but it represents
tossing the legacy PM stuff. at
* William Lee Irwin III [EMAIL PROTECTED] wrote:
It does largely achieve the sort of fairness it set out for itself as
its design goal. One should also note that the queueing mechanism is
more than flexible enough to handle prioritization by a number of
different methods, and the large
On Wed, 18 Apr 2007 10:22:59 -0700 (PDT)
Linus Torvalds [EMAIL PROTECTED] wrote:
So if you have 2 users on a machine running CPU hogs, you should
*first* try to be fair among users. If one user then runs 5 programs,
and the other one runs just 1, then the *one* program should get 50%
of the
On Wed, 18 Apr 2007, Bill Davidsen wrote:
Robert P. J. Day wrote:
...
um ... what does APM have to do with legacy PM? two different
issues, no?
Since the patches are going into apm.c and apm was used for suspend
and poweroff before ACPI was a feature of the hardware, I assume
there's a
El Wed, 18 Apr 2007 10:22:59 -0700 (PDT), Linus Torvalds [EMAIL PROTECTED]
escribió:
So if you have 2 users on a machine running CPU hogs, you should *first*
try to be fair among users. If one user then runs 5 programs, and the
other one runs just 1, then the *one* program should get 50% of
On Wed, 2007-04-18 at 11:19 +0200, Miklos Szeredi wrote:
Allowing this and other flags to NOT be propagated just makes it
possible to have a set of shared mounts with asymmetric properties,
which may actually be desirable.
The shared mount feature was designed to ensure that the
On Wed, 2007-04-18 at 16:01 +0100, Christoph Hellwig wrote:
I suspect the right answer here is to make nfs mount handling smarter.
The way mounting works the filesystem is allowed to choose whether it
can re-used a superblock or needs a new one. In the NFS case we probably
want to allow
501 - 600 of 738 matches
Mail list logo
