On Mon, 23 Apr 2007, Christoph Lameter wrote:
Obvious fix. It was broken by
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=f2a2a7108aa0039ba7a5fe7a0d2ecef2219a7584
Dec 7. So its in 2.6.20 and later. Candiate for stable?
I agree it's obvious enough that it
Srinivasa Ds writes:
+ } else {\
+ char dot_name[KSYM_NAME_LEN+1]; \
+ dot_name[0] = '.'; \
+ dot_name[1] = '\0';
Christoph Hellwig writes:
The first question is obviously, is this really something we want?
spawning kernel thread on demand without reaping them properly seems
quite dangerous.
What specifically has to be done to reap a kernel thread? Are you
concerned about the number of threads, or about
On Sun, 22 Apr 2007 19:00:46 -0700, Eric Hopper
[EMAIL PROTECTED] said:
I know that this whole effort has been put in disarray by the
prosecution of Hans Reiser, but I'm curious as to its status. Is
Reiser4 going to be going into the Linus kernel anytime soon? Is there
somewhere I should be
Roland McGrath wrote:
I have to admit I still don't really understand all this. Is it
documented somewhere?
I have explained it in public more than once, but I don't know off hand
anywhere that was helpfully recorded.
Thanks very much. I'd been poking about, but the closest I
Arjan van de Ven wrote:
Within reason, it's not the number of clients that X has that causes its
CPU bandwidth use to sky rocket and cause problems. It's more to to
with what type of clients they are. Most GUIs (even ones that are
constantly updating visual data (e.g. gkrellm -- I can open
Hey,
is it right, that the NX Bit is not used under i386-Arch but under x86_64-Arch?
When yes, is there a special argument for it not to be used?
Ciao Thilo
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
On Sun, Apr 22, 2007 at 11:12:13PM -0600, Eric W. Biederman wrote:
Currently because vmlinux does not reflect that the kernel is relocatable
we still have to support CONFIG_PHYSICAL_START. So this patch adds a small
c program to do what we cannot do with a linker script, set the elf header
* Peter Williams [EMAIL PROTECTED] wrote:
The cases are fundamentally different in behavior, because in the
first case, X hardly consumes the time it would get in any scheme,
while in the second case X really is CPU bound and will happily
consume any CPU time it can get.
Which
On Tue, 24 Apr 2007, Cestonaro, Thilo (external) wrote:
Hey,
is it right, that the NX Bit is not used under i386-Arch but under x86_64-Arch?
When yes, is there a special argument for it not to be used?
Ciao Thilo
I don't think so - some i386 cpus definitely have support for the NX bit.
On Thu, 15 Mar 2007 16:46:39 +0100 Gerd Hoffmann [EMAIL PROTECTED] wrote:
The console subsystem already has an idea of a boot console, using the
CON_BOOT flag. The implementation has some flaws though. The major
problem is that presence of a boot console makes register_console()
ignore any
Paul Mackerras wrote:
Srinivasa Ds writes:
+} else {\
+char dot_name[KSYM_NAME_LEN+1]; \
+dot_name[0] = '.'; \
+dot_name[1] = '\0';
On Tue, 27 Mar 2007 14:49:20 -0700 Jeremy Fitzhardinge [EMAIL PROTECTED]
wrote:
The softlockup watchdog is currently a nuisance in a virtual machine,
since the whole system could have the CPU stolen from it for a long
period of time. While it would be unlikely for a guest domain to be
* Ed Tomlinson [EMAIL PROTECTED] wrote:
SD 0.46 1-2 FPS
cfs v5 nice -19 219-233 FPS
cfs v5 nice 0 1000-1996
cfs v5 nice -10 60-65 FPS
the problem is, the glxgears portion of this test is an _inverse_
testcase.
The reason? glxgears on true 3D hardware will
Andrew Morton wrote:
On Tue, 27 Mar 2007 14:49:20 -0700 Jeremy Fitzhardinge [EMAIL PROTECTED]
wrote:
The softlockup watchdog is currently a nuisance in a virtual machine,
since the whole system could have the CPU stolen from it for a long
period of time. While it would be unlikely for
On Tuesday 24 April 2007, Ingo Molnar wrote:
* Peter Williams [EMAIL PROTECTED] wrote:
The cases are fundamentally different in behavior, because in the
first case, X hardly consumes the time it would get in any scheme,
while in the second case X really is CPU bound and will happily
Ingo Molnar wrote:
static void
yield_task_fair(struct rq *rq, struct task_struct *p, struct task_struct *p_to)
{
struct rb_node *curr, *next, *first;
struct task_struct *p_next;
/*
* yield-to support: if we are on the same runqueue then
* give half of
* Gene Heskett [EMAIL PROTECTED] wrote:
Gene has done some testing under CFS with X reniced to +10 and the
desktop still worked smoothly for him.
As a data point here, and probably nothing to do with X, but I did
manage to lock it up, solid, reset button time tonight, by wanting
On Tue, 2007-04-24 at 12:58 +1000, Neil Brown wrote:
On Friday April 20, [EMAIL PROTECTED] wrote:
Scale writeback cache per backing device, proportional to its writeout
speed.
So it works like this:
We account for writeout in full pages.
When a page has the Writeback flag cleared,
On Mon, 23 Apr 2007 23:58:20 -0700 Jeremy Fitzhardinge [EMAIL PROTECTED]
wrote:
Andrew Morton wrote:
On Tue, 27 Mar 2007 14:49:20 -0700 Jeremy Fitzhardinge [EMAIL PROTECTED]
wrote:
The softlockup watchdog is currently a nuisance in a virtual machine,
since the whole system could
How do you send a reply to an email you have deleted?
--
[EMAIL PROTECTED]
--
http://www.fastmail.fm - I mean, what is it about a decent email service?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
On Tuesday 24 April 2007, Ingo Molnar wrote:
* Gene Heskett [EMAIL PROTECTED] wrote:
Gene has done some testing under CFS with X reniced to +10 and the
desktop still worked smoothly for him.
As a data point here, and probably nothing to do with X, but I did
manage to lock it up, solid,
* Gene Heskett [EMAIL PROTECTED] wrote:
(Btw., to protect against such mishaps in the future i have changed
the SysRq-N [SysRq-Nice] implementation in my tree to not only
change real-time tasks to SCHED_OTHER, but to also renice negative
nice levels back to 0 - this will show up in
On Tue, 24 Apr 2007, Ingo Molnar wrote:
* Gene Heskett [EMAIL PROTECTED] wrote:
Gene has done some testing under CFS with X reniced to +10 and the
desktop still worked smoothly for him.
As a data point here, and probably nothing to do with X, but I did
manage to lock it up, solid, reset
Vivek Goyal [EMAIL PROTECTED] writes:
On Sun, Apr 22, 2007 at 11:12:13PM -0600, Eric W. Biederman wrote:
Currently because vmlinux does not reflect that the kernel is relocatable
we still have to support CONFIG_PHYSICAL_START. So this patch adds a small
c program to do what we cannot do
* David Lang [EMAIL PROTECTED] wrote:
(Btw., to protect against such mishaps in the future i have changed
the SysRq-N [SysRq-Nice] implementation in my tree to not only
change real-time tasks to SCHED_OTHER, but to also renice negative
nice levels back to 0 - this will show up in -v6.
* Ingo Molnar [EMAIL PROTECTED] wrote:
yeah, i guess this has little to do with X. I think in your scenario
it might have been smarter to either stop, or to renice the workloads
that took away CPU power from others to _positive_ nice levels.
Negative nice levels can indeed be dangerous.
* Rogan Dawes [EMAIL PROTECTED] wrote:
if (p_to p-wait_runtime 0) {
p-wait_runtime = 1;
p_to-wait_runtime += p-wait_runtime;
}
the above is the basic expression of: charge a positive bank balance.
[..]
[note, due to the
Mel-san.
I tested your patch (Thanks!). It worked. But..
In my understanding, why ia64 doesn't use early_param() macro for mem= at el.
is that
it has to use mem= option at efi handling which is called before
parse_early_param().
Current ia64's boot path is
setup_arch()
- efi
* Ingo Molnar [EMAIL PROTECTED] wrote:
[...] That way you'd only have had to hit SysRq-N to get the system
out of the wedge.)
small correction: Alt-SysRq-N.
Ingo
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
Hi,
socket buffers were not always freed when receiving multicasts
Bye,
--
Markus Pietrek
Lead Software Engineer
Phone: +49-7667-908-501, Fax: +49-7667-908-200
mailto:[EMAIL PROTECTED]
FS Forth-Systeme GmbH
A Digi International Company
Kueferstr. 8, 79206 Breisach, Germany
Tax: 07008/12000 /
Hello,
I have tried the cfs patches with 2.6.20.7 in the last days.
I am using KDE 3.5.6, gentoo unstable and have a dual core AMD64 system with
1GB ram and a nvidia card (using the closed source drivers, yes I suck, but I
love playing 3d games once in a while).
I don't have interactivity
Hi list,
with cfs-v5 finally booting on my machine I have run my daily
numbercrunching jobs on both cfs-v5 and sd-0.46, 2.6.21-v7 on
top of a stock openSUSE 10.2 (X86_64). Config for both kernel
is the same except for the X boost option in cfs-v5 which on
my system didn't work (X still was @ -19;
On Tue, 24 Apr 2007 15:00:42 +1000,
Benjamin Herrenschmidt [EMAIL PROTECTED] wrote:
Like anything else, modules should have separated the entrypoints for
- Initiating a removal request
- Releasing the module
The former is use did rmmod, can unregister things from subsystems,
etc...
On 4/24/07, William Heimbigner [EMAIL PROTECTED] wrote:
On Tue, 24 Apr 2007, Cestonaro, Thilo (external) wrote:
Hey,
is it right, that the NX Bit is not used under i386-Arch but
under x86_64-Arch?
When yes, is there a special argument for it not to be used?
Ciao Thilo
I don't think so -
Hi Hal,
you are correct,
with the current firmware version it will fail later.
Christoph R.
[EMAIL PROTECTED] wrote on 23.04.2007 18:55:59:
Hi Joachim,
On Mon, 2007-04-23 at 12:23, Joachim Fenkes wrote:
Add Modify Port verb support to eHCA driver.
ib_cm needs this to initialize
On Mon, 2007-04-23 at 10:45 -0700, Andrew Morton wrote:
Andrew: I plan to add patches 1-5 to the for-andrew branch of the
git390 repository if that is fine with you. The only thing that will
be missing in the tree is the patch that disables wireless for s390.
The code does compile but
* Michael Gerdau [EMAIL PROTECTED] wrote:
I'm running three single threaded perl scripts that do double
precision floating point math with little i/o after initially loading
the data.
thanks for the testing!
What I also don't understand is the difference in load average, sd
constantly
Question: is there some reason that kconfig does not allow for default
governors of conservative/ondemand/powersave?
I'm not aware of any reason why one of those governors could not be used
as default.
William Heimbigner
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line
On Tue, 24 Apr 2007, Herbert Xu wrote:
Hmm, *sigh*. I guess the patch below fixes the problem, but it is a
masterpiece in the field of ugliness. And I am not sure whether it is
completely correct either. Are there any immediate ideas for better
solution with respect to how struct sock
Hello,
Kristen Carlson Accardi wrote:
static unsigned int ata_print_id = 1;
@@ -1744,6 +1745,23 @@ int ata_dev_configure(struct ata_device
}
dev-cdb_len = (unsigned int) rc;
+ /*
+ * check to see if this ATAPI device supports
+
+ /*
+ * check to see if this ATAPI device supports
+ * Asynchronous Notification
+ */
+ if ((ap-flags ATA_FLAG_AN) ata_id_has_AN(id))
+ {
Bracketing police ^^^
+ /* issue SET feature command
Kristen Carlson Accardi wrote:
+static struct disk_attribute disk_attr_capability = {
+ .attr = {.name = capability_flags, .mode = S_IRUGO },
+ .show = disk_capability_read
+};
How about just capability? I think that would be more consistent with
other attributes.
--
tejun
-
To
+ /* check the 'N' bit in word 0 of the FIS */
+ if (f[0] (1 15)) {
+ int port_addr = ((f[0] 0x0f00) 8);
+ struct ata_device *adev = ap-device[port_addr];
You can't be sure that the port_addr returned will be in range if
Hi,
If you add support for let's say [tifm_8xx2] in the future, which
would have port offsets different that [tifm_7xx1], you would also need a
completely new modules for slots (sd, ms, etc).
Does not this constitutes an unbounded speculation?
Only time will tell :)
And then, what would you
Ulrich Drepper a écrit :
It looks mostly good. I wouldn't use the high bit to differentiate
the 64-bit operations, though. Since we do not allow to apply it to
all operations the only effect will be that the compiler has a harder
time generating the code for the switch statement. If you use
On Sun, 8 Apr 2007 14:35:59 -0700, Andrew Morton [EMAIL PROTECTED] wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/
- Lots of x86 updates
Has somthing related with PTY's changed in this kernel ?
I have to enable legacy PTY handling in a
At 11:47 07/04/24, Nick Piggin wrote:
As Hugh points out, we must have atomic ops here, so changing the generic
code to use the __ version is wrong. However if there is a faster way that
i386 can perform the atomic variant, then doing so will speed up the generic
code without breaking other
On Fri, 20 Apr 2007 18:51:13 +0900
Keiichi KII [EMAIL PROTECTED] wrote:
I started to do some cleanups and fixups here, but abandoned it when it was
all getting a bit large.
Here are some fixes against this patch:
I'm going to fix my patches by following your reviews and send new patches
on
We don't really have anything that corresponds to netpoll's
connections at higher levels.
I'm tempted to say we should make this work more like the dummy
network device. ie:
modprobe netconsole -o netcon1 [params]
modprobe netconsole -o netcon2 [params]
The configuration of netconsole's looks
layer tree:
git://git.kernel.dk/data/git/linux-2.6-block.git
and I've uploaded a rolled up version here as well:
http://brick.kernel.dk/snaps/cfq-update-20070424
The patch series is essentially a series of cleanups and smaller
optimizations, but there's also a larger change in there (patches 4
When testing the syslet async io approach, I discovered that CFQ
sometimes didn't perform as well as expected. cfq_should_preempt()
needs to better check for cooperating tasks, so fix that by allowing
preemption of an equal priority queue if the recently queued request
is as good a candidate for
- Implement logic for detecting cooperating processes, so we
choose the best available queue whenever possible.
- Improve residual slice time accounting.
- Remove dead code: we no longer see async requests coming in on
sync queues. That part was removed a long time ago. That means
that we
What I also don't understand is the difference in load average, sd
constantly had higher values, the above figures are representative for
the whole log. I don't know which is better though.
hm, it's hard from here to tell that. What load average does the vanilla
kernel report? I'd
* Bill Davidsen [EMAIL PROTECTED] wrote:
The small attached script does a nice job of showing animation
glitches in the glxgears animation. I have run one set of tests, and
will have several more tomorrow. I'm off to a poker game, and would
like to let people draw their own conclusions.
- Move the queue_new flag clear to when the queue is selected
- Only select the non-first queue in cfq_get_best_queue(), if there's
a substantial difference between the best and first.
- Get rid of -busy_rr
- Only select a close cooperator, if the current queue is known to take
a while to
We can track it fairly accurately locally, let the slice handling
take care of the rest.
Signed-off-by: Jens Axboe [EMAIL PROTECTED]
---
block/cfq-iosched.c |6 +-
1 files changed, 1 insertions(+), 5 deletions(-)
diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
index
For cases where the rbtree is mainly used for sorting and min retrieval,
a nice speedup of the rbtree code is to maintain a cache of the leftmost
node in the tree.
Also spotted in the CFS CPU scheduler code.
Signed-off-by: Jens Axboe [EMAIL PROTECTED]
---
block/cfq-iosched.c | 62
Signed-off-by: Jens Axboe [EMAIL PROTECTED]
---
block/cfq-iosched.c | 66 ++
1 files changed, 50 insertions(+), 16 deletions(-)
diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
index e6cc77f..f86ff4d 100644
--- a/block/cfq-iosched.c
+++
Signed-off-by: Jens Axboe [EMAIL PROTECTED]
---
block/cfq-iosched.c | 31 ++-
1 files changed, 18 insertions(+), 13 deletions(-)
diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
index f920527..772df89 100644
--- a/block/cfq-iosched.c
+++ b/block/cfq-iosched.c
Drawing on some inspiration from the CFS CPU scheduler design, overhaul
the pending cfq_queue concept list management. Currently CFQ uses a
doubly linked list per priority level for sorting and service uses.
Kill those lists and maintain an rbtree of cfq_queue's, sorted by when
to service them.
It's only used for preemption now that the IDLE and RT queues also
use the rbtree. If we pass an 'add_front' variable to
cfq_service_tree_add(), we can set -rb_key to 0 to force insertion
at the front of the tree.
Signed-off-by: Jens Axboe [EMAIL PROTECTED]
---
block/cfq-iosched.c | 87
Currently CFQ does a linked insert into the current list for RT
queues. We can just factor the class into the rb insertion,
and then we don't have to treat RT queues in a special way. It's
faster, too.
Signed-off-by: Jens Axboe [EMAIL PROTECTED]
---
block/cfq-iosched.c | 27
This is probably a
reasonable thing to do but it doesn't feel like the right place. I
think get_dirty_limits should return the raw threshold, and
balance_dirty_pages should do both tests - the bdi-local test and the
system-wide test.
Ok, that makes sense I guess.
Well, my narrow
Same treatment as the RT conversion, just put the sorted idle
branch at the end of the tree.
Signed-off-by: Jens Axboe [EMAIL PROTECTED]
---
block/cfq-iosched.c | 67 +++---
1 files changed, 31 insertions(+), 36 deletions(-)
diff --git
Use the max_slice-cur_slice as the multipler for the insertion offset.
Signed-off-by: Jens Axboe [EMAIL PROTECTED]
---
block/cfq-iosched.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
index f86ff4d..251131a 100644
---
We don't enable it by default, don't let it get enabled during
runtime.
Signed-off-by: Jens Axboe [EMAIL PROTECTED]
---
block/cfq-iosched.c |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
index 8f76aed..f920527 100644
---
* Michael Gerdau [EMAIL PROTECTED] wrote:
so to be totally 'fair' and get the same rescheduling 'granularity'
you should probably lower CFS's sched_granularity_ns to 2 msecs.
I'll change default nice in cfs to -10.
I'm also happy to adjust /proc/sys/kernel/sched_granularity_ns to
We don't use it anymore in the slice expiry handling.
Signed-off-by: Jens Axboe [EMAIL PROTECTED]
---
block/cfq-iosched.c | 28 +---
1 files changed, 13 insertions(+), 15 deletions(-)
diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
index 2d0e9c5..b680002 100644
For tagged devices, allow overlap of requests if the idle window
isn't enabled on the current active queue.
Signed-off-by: Jens Axboe [EMAIL PROTECTED]
---
block/cfq-iosched.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
Kristen Carlson Accardi wrote:
Send an uevent to user space to indicate that a media change event has
occurred.
Signed-off-by: Kristen Carlson Accardi [EMAIL PROTECTED]
Index: 2.6-git/block/genhd.c
===
---
Ingo Molnar wrote:
* Rogan Dawes [EMAIL PROTECTED] wrote:
if (p_to p-wait_runtime 0) {
p-wait_runtime = 1;
p_to-wait_runtime += p-wait_runtime;
}
the above is the basic expression of: charge a positive bank balance.
[..]
[note, due to the
On Tue, 24 Apr 2007 17:14:28 +0900 Keiichi KII [EMAIL PROTECTED] wrote:
On Fri, 20 Apr 2007 18:51:13 +0900
Keiichi KII [EMAIL PROTECTED] wrote:
I started to do some cleanups and fixups here, but abandoned it when it
was
all getting a bit large.
Here are some fixes against this
On Tue, 2007-04-24 at 10:19 +0200, Miklos Szeredi wrote:
This is probably a
reasonable thing to do but it doesn't feel like the right place. I
think get_dirty_limits should return the raw threshold, and
balance_dirty_pages should do both tests - the bdi-local test and the
Hi William,
On 24/04/07, William Heimbigner [EMAIL PROTECTED] wrote:
Question: is there some reason that kconfig does not allow for default
governors of conservative/ondemand/powersave?
Performance?
I'm not aware of any reason why one of those governors could not be used
as default.
My
On Tue, Apr 24, 2007 at 03:55:06PM +1000, Paul Mackerras wrote:
Christoph Hellwig writes:
The first question is obviously, is this really something we want?
spawning kernel thread on demand without reaping them properly seems
quite dangerous.
What specifically has to be done to reap a
Here i'm assuming that the vmstats are directly comparable: that your
number-crunchers behave the same during the full runtime - is that
correct?
Yes, basically it does (disregarding small fluctuations)
I'll see whether I can produce some type of absolute performance
measure as well.
* Michael Gerdau [EMAIL PROTECTED] wrote:
Here i'm assuming that the vmstats are directly comparable: that
your number-crunchers behave the same during the full runtime - is
that correct?
Yes, basically it does (disregarding small fluctuations)
ok, good.
I'll see whether I can
The following patch fixes double free manifesting itself as crash in
__rcu_process_callbasks():
http://marc.info/?l=linux-kernelm=117518764517017w=2
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229112
The problem is with check_dead_utrace() conditionally scheduling
struct utrace for
oh, you are writing the number-cruncher?
Yep.
In general the 'best'
performance metrics for scheduler validation are the ones where you have
immediate feedback: i.e. some ops/sec (or ops per minute) value in some
readily accessible place, or some milliseconds-per-100,000 ops type of
This is probably a
reasonable thing to do but it doesn't feel like the right place. I
think get_dirty_limits should return the raw threshold, and
balance_dirty_pages should do both tests - the bdi-local test and the
system-wide test.
Ok, that makes sense I guess.
David Schwartz пишет:
You have a misunderstanding about the semantics of 'sendfile'.
The 'sendfile' function is just a more efficient version of a
read followed by a write. If you did a read followed by a write,
it would block as well (in the read).
DS
sendfile function is not just
On Tue, 2007-04-24 at 11:14 +0200, Miklos Szeredi wrote:
I'm still not quite sure what purpose the above soft limiting
serves. It seems to just give advantage to writers, which managed to
accumulate lots of dirty pages, and then can convert that into even
more dirtyings.
The
On Mon, Apr 23, 2007 at 03:18:19PM -0700, Greg KH wrote:
On Mon, Apr 23, 2007 at 11:48:47PM +0200, Adrian Bunk wrote:
This email lists some known regressions in Linus' tree compared to 2.6.20.
If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer
Pavel Emelianov wrote:
Implement try_to_free_pages_in_container() to free the
pages in container that has run out of memory.
The scan_control-isolate_pages() function isolates the
container pages only.
Pavel,
I've just started playing around with these patches, I preferred
the approach of
Ahh, now I see; I had totally blocked out these few lines:
pages_written += write_chunk - wbc.nr_to_write;
if (pages_written = write_chunk)
break; /* We've done our duty */
yeah, those look dubious
Roland,
can you please help with it?
current utrace state is far from being stable,
RHEL5 and -mm kernels can be quite easily crashed with some of the exploits
we collected so far.
Alexey can help you with any information needed - call traces, test cases,
but without your help we can't fix it all
Subject: Check zone boundaries when freeing bootmem
Zone boundaries do not have to be aligned to MAX_ORDER_NR_PAGES.
Hmm. I don't understand here yet... Could you explain more?
This issue occurs only when ZONE_MOVABLE is specified.
If its boundary is aligned to MAX_ORDER automatically,
I
Signed-off-by: Matt Reimer [EMAIL PROTECTED]
Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED]
---
drivers/w1/w1_int.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/w1/w1_int.c b/drivers/w1/w1_int.c
index 357a2e0..258defd 100644
--- a/drivers/w1/w1_int.c
+++
On Tue, 24 Apr 2007 11:47:20 +0200 Miklos Szeredi [EMAIL PROTECTED] wrote:
Ahh, now I see; I had totally blocked out these few lines:
pages_written += write_chunk - wbc.nr_to_write;
if (pages_written = write_chunk)
Signed-off-by: Matt Reimer [EMAIL PROTECTED]
Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED]
---
drivers/w1/masters/Kconfig |8 +
drivers/w1/masters/Makefile |2 +-
drivers/w1/masters/ds1wm.c | 463 +++
include/linux/ds1wm.h | 13 ++
4
On Tue, 24 Apr 2007, Yasunori Goto wrote:
Subject: Check zone boundaries when freeing bootmem
Zone boundaries do not have to be aligned to MAX_ORDER_NR_PAGES.
Hmm. I don't understand here yet... Could you explain more?
Nodes are required to be MAX_ORDER_NR_PAGES aligned for the buddy
On Fri, 13 Apr 2007 21:13:13 -0600 [EMAIL PROTECTED] (Eric W. Biederman) wrote:
This patch reworks kthread_stop so it is more flexible and it causes
the target kthread to abort interruptible sleeps. Allowing a larger
class of kernel threads to use to the kthread API.
The changes start by
On Tue, 2007-04-24 at 03:00 -0700, Andrew Morton wrote:
On Tue, 24 Apr 2007 11:47:20 +0200 Miklos Szeredi [EMAIL PROTECTED] wrote:
Ahh, now I see; I had totally blocked out these few lines:
pages_written += write_chunk - wbc.nr_to_write;
if
Hisashi Hifumi wrote:
At 11:47 07/04/24, Nick Piggin wrote:
As Hugh points out, we must have atomic ops here, so changing the generic
code to use the __ version is wrong. However if there is a faster way
that
i386 can perform the atomic variant, then doing so will speed up the
generic
Ahh, now I see; I had totally blocked out these few lines:
pages_written += write_chunk - wbc.nr_to_write;
if (pages_written = write_chunk)
break; /* We've done our duty
*/
Sorry for replying to Alan's reply, I missed the original mail.
+#define ata_id_has_AN(id) \
+ ((id[76] (~id[76])) ((id)[78] (1 5)))
(a ~a) (b 32)
I don't think that does what you think it does, because at that point
it's a funny way to write 0 ((0 or 1) binary-and (0 or 32)).
On Tue, 2007-04-24 at 12:19 +0200, Miklos Szeredi wrote:
Ahh, now I see; I had totally blocked out these few lines:
pages_written += write_chunk - wbc.nr_to_write;
if (pages_written = write_chunk)
On Sun, 22 Apr 2007 20:48:08 +0200 Rafael J. Wysocki [EMAIL PROTECTED]
wrote:
Make it possible to register suspend notifiers so that subsystems can perform
suspend-related operations that should not be carried out by device drivers'
.suspend() and .resume() routines.
x86_64 allnoconfig:
Andrew Morton [EMAIL PROTECTED] writes:
On Fri, 13 Apr 2007 21:13:13 -0600 [EMAIL PROTECTED] (Eric W. Biederman)
wrote:
This patch reworks kthread_stop so it is more flexible and it causes
the target kthread to abort interruptible sleeps. Allowing a larger
class of kernel threads to use to
1 - 100 of 911 matches
Mail list logo
