* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> On Tue, 27 Feb 2007, Ingo Molnar wrote:
> >
> > update: Jeff sent me 3 pending forcedeth.c fixes, and they indeed
> > fix the regression. The one that fixed it is:
>
> Ok, that was included in the bunch I just pulled and pushed out, so
>
Linus Torvalds wrote:
> Oh well.. I'm not very proud of this, because quite frankly, -rc2 has way
> more changes than I really like.
>
Hi Linus,
rc2 fails to build on my thinkpad t43:
CC arch/i386/kernel/io_apic.o
arch/i386/kernel/io_apic.c: In function 'setup_IO_APIC_irqs':
Initialize affinity only when building SMP kernels.
Signed-off-by: Fernando Luis Vazquez Cao <[EMAIL PROTECTED]>
---
--- linux-2.6.21-rc2-dtt/arch/i386/kernel/io_apic.c 2007-03-06
15:20:14.0 +0900
+++ linux-2.6.21-rc2-kdump/arch/i386/kernel/io_apic.c 2007-03-06
15:51:45.0
Initialize affinity only when building SMP kernels.
Signed-off-by: Fernando Luis Vazquez Cao <[EMAIL PROTECTED]>
---
--- linux-2.6.21-rc2-dtt/arch/x86_64/kernel/io_apic.c 2007-03-06
15:20:14.0 +0900
+++ linux-2.6.21-rc2-kdump/arch/x86_64/kernel/io_apic.c 2007-03-06
15:48:52.0
Initialize affinity only when building SMP kernels.
Signed-off-by: Fernando Luis Vazquez Cao <[EMAIL PROTECTED]>
---
--- linux-2.6.21-rc2-dtt/arch/x86_64/kernel/io_apic.c 2007-03-06
15:20:14.0 +0900
+++ linux-2.6.21-rc2-kdump/arch/x86_64/kernel/io_apic.c 2007-03-06
15:48:52.0
Initialize affinity only when building SMP kernels.
Signed-off-by: Fernando Luis Vazquez Cao <[EMAIL PROTECTED]>
---
--- linux-2.6.21-rc2-dtt/arch/i386/kernel/io_apic.c 2007-03-06
15:20:14.0 +0900
+++ linux-2.6.21-rc2-kdump/arch/i386/kernel/io_apic.c 2007-03-06
15:51:45.0
Initialize affinity only when building SMP kernels.
Signed-off-by: Fernando Luis Vazquez Cao <[EMAIL PROTECTED]>
---
--- linux-2.6.21-rc2-dtt/arch/i386/kernel/io_apic.c 2007-03-06
15:20:14.0 +0900
+++ linux-2.6.21-rc2-kdump/arch/i386/kernel/io_apic.c 2007-03-06
15:51:45.0
Fernando Luis Vázquez Cao <[EMAIL PROTECTED]> writes:
> Initialize affinity only when building SMP kernels.
Reasonable. I goofed here.
However I would prefer my patch that just deletes these problem lines.
These lines don't really contribute anything and are harmless to
remove.
Eric
-
To
On 2/27/07, Linus Torvalds <[EMAIL PROTECTED]> wrote:
Oh well.. I'm not very proud of this, because quite frankly, -rc2 has way
more changes than I really like.
And yeah, it's largely my fault, because I simply missed a V4L/DVB merge
that came in before the merge window closed, but since I
Arnd Bergmann <[EMAIL PROTECTED]> writes:
>
> Introducing the irq_request() etc. functions that take a struct irq*
> instead of an int sounds good, but I'd hope we can avoid using those
> in device drivers and do a separate abstraction for each bus_type
> that deals with interrupts. I'm not sure
On Tue, Feb 27, 2007 at 08:47:55PM -0800, Pallipadi, Venkatesh wrote:
> >I played with this a little, and got puzzled.
> >My quad core box used exactly the same amount of power whether the
> >'ladder' governer was loaded & in use or not. In both situations
> >it was exactly the same as a
> It's most likely a red herring, lots of config changes
> make the bug go away on some kernel versions (but not
> on others); the problem is very sensitive to changes in
> memory layout.
I wouldn't be that sure ... I've had problems in the past with PMU based
cpufreq... looks like flushing all
Hmm.. I seem to have failed to send out this reply a few days ago :(
Linus Torvalds <[EMAIL PROTECTED]> writes:
> On Wed, 21 Feb 2007, Andrew Morton wrote:
>> >
>> >
>
"Lu, Yinghai" <[EMAIL PROTECTED]> writes:
>
> Why not use
>
> IRQ0_VECTOR... IRQ15_VECTOR here.
I do by the end of the patch series it was a patch ordering issue.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
> Hello,
>> - encrypts new files depending on their filename, and generally
>
> What about renaming a file ???
Well, that's a small (but known!) problem with this scheme.
If you say that everything below a directory "_crypt_" should be
encrypted, and just move files in there, you've got no
Linus Torvalds wrote:
Oh well.. I'm not very proud of this, because quite frankly, -rc2 has way
more changes than I really like.
I got this warning so far :)
drivers/video/Kconfig:1622:warning: 'select' used by config symbol
'FB_PS3' refer to undefined symbol 'PS3_PS3AV'
Regards,
Oh well.. I'm not very proud of this, because quite frankly, -rc2 has way
more changes than I really like.
And yeah, it's largely my fault, because I simply missed a V4L/DVB merge
that came in before the merge window closed, but since I didn't notice it
didn't make -rc1, and as such it got
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
arch/i386/kernel/ldt.c |2 +-
arch/x86_64/kernel/ldt.c |2 +-
kernel/fork.c|4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/i386/kernel/ldt.c b/arch/i386/kernel/ldt.c
index
>-Original Message-
>From: Dave Jones [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, February 27, 2007 8:44 AM
>To: Pallipadi, Venkatesh
>Cc: linux-kernel; Andrew Morton; linux-acpi@vger.kernel.org;
>Adam Belay; Li, Shaohua; Brown, Len
>Subject: Re: [PATCH 1/3]cpuidle take2: Core cpuidle
Hi,
I am reading the source code AS scheduler in 2.6.18(as-ioscheduler.c).
In function as_close_req, variable delay is in millisecond, while
ad->antic_expire is in jiffies. Doesn't the comparison of delay and
ad->antic_expire make any problem?
The related source code is quoted blow:
if
(hrmph. having to copy/paste/try again. evolution seems to be broken..
RCPT TO <[EMAIL PROTECTED]> failed: Cannot resolve your domain {mp049}
..caused me to be unable to send despite receipts being disabled)
On Wed, 2007-02-28 at 09:58 +1100, Con Kolivas wrote:
> On Tuesday 27 February 2007
On 2/28/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Fri, 23 Feb 2007 21:10:36 +0530 "Aneesh Kumar K.V" <[EMAIL PROTECTED]>
wrote:
> From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
>
> Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
> ---
> arch/i386/kernel/ldt.c |2 +-
>
patch against lastest mm tree.
- Currently after path_lookup succeed we dot't have any guarantie what
it is DIR. This must be explicitly demanded.
- path_lookup can't return negative dentry, So inode check is useless.
Signed-off-by: Dmitriy Monakhov <[EMAIL PROTECTED]>
diff --git
On Tue, Feb 27, 2007 at 09:36:23PM -0500, Bill Davidsen wrote:
> Florin Iucha wrote:
> >Hello, it's me and my 70 GB of photos again.
> >
> >I have tested both CIFS and NFSv4 clients in kernel 2.6.20-rc1 . CIFS
> >passed with flying colors and NFSv4 stalled after 7 GB.
> Neil has been diddling
On Wed, Feb 28, 2007 at 08:31:13AM +0530, Srivatsa Vaddagiri wrote:
> This problem (of kthread_stopping a frozen thread) was there when we
> implemented freezer-based cpu hotplug. We worked around that in the
> callbacks by thawing the worker thread first before kthread_stopping it,
> which is
From: Divy Le Ray <[EMAIL PROTECTED]>
This patch adds a "-ko" tag to the driver version.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/version.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/cxgb3/version.h
On Wed, Feb 28, 2007 at 12:57:35AM +0100, Rafael J. Wysocki wrote:
> > How about other kthread_stop()s ? For example,
> > kernel/softirq.c:cpu_callback() ?
>
> They all are PF_NOFREEZE, I suppose. If we make all workqueues nonfreezable
> (as they were before), the problem won't appear.
We can
On 2/27/07, Theodore Tso <[EMAIL PROTECTED]> wrote:
I think what you are not hearing, and what everyone else is saying
(INCLUDING Linus), is that for most programmers, state machines are
much, much harder to program, understand, and debug compared to
multi-threaded code. You may disagree (were
On Tue, Feb 27, 2007 at 10:51:27PM +0100, Rafael J. Wysocki wrote:
> We have a problem with freezable workqueues in 2.6.21-rc1 and in -mm
> (there are only two of them, in XFS, but still). Namely, their worker threads
> deadlock with workqueue_cpu_callback() that gets called during the CPU
>
On 2/27/07, Bill Davidsen <[EMAIL PROTECTED]> wrote:
Paulo Marques wrote:
> Rik van Riel wrote:
>> J.A. Magallón wrote:
>>> [...]
>>> Its the same to answer 4+4 queries than 8 at half the speed, isn't it ?
>>
>> That still doesn't fix the potential Linux problem that this
>> benchmark
On 2/27/07, Nick Piggin <[EMAIL PROTECTED]> wrote:
Nish Aravamudan wrote:
> On 2/26/07, Nick Piggin <[EMAIL PROTECTED]> wrote:
>
>> Rik van Riel wrote:
>> > Lorenzo Allegrucci wrote:
>> >
>> >> Hi lkml,
>> >>
>> >> according to the test below (sysbench) Linux seems to have scalability
>> >>
Linus Torvalds wrote:
On Mon, 26 Feb 2007, Rene Herman wrote:
Other than these two, ECP parallel ports are the other remaining users.
Now, even though on a machine that still has a parallel port it might usually
indeed be set to ECP in its BIOS; having anything attached to the port also
use it
Florin Iucha wrote:
Hello, it's me and my 70 GB of photos again.
I have tested both CIFS and NFSv4 clients in kernel 2.6.20-rc1 . CIFS
passed with flying colors and NFSv4 stalled after 7 GB.
Configuration:
Server: PIII/1GHz, 512 MB RAM, Debian testing,
distro kernel
[EMAIL PROTECTED] wrote:
Hello!
I'm experiencing extreme lags during disk writes. I have read somewhere (didn't
save the URI, sigh) that this is actually related to bad (non-existing) write
io priorities (CFQ only manages file reads).
I could imagine two quick, easy and probably quite
Nish Aravamudan wrote:
On 2/26/07, Nick Piggin <[EMAIL PROTECTED]> wrote:
Rik van Riel wrote:
> Lorenzo Allegrucci wrote:
>
>> Hi lkml,
>>
>> according to the test below (sysbench) Linux seems to have scalability
>> problems beyond 8 client threads:
>>
Paulo Marques wrote:
Rik van Riel wrote:
J.A. Magallón wrote:
[...]
Its the same to answer 4+4 queries than 8 at half the speed, isn't it ?
That still doesn't fix the potential Linux problem that this
benchmark identified.
To clarify: I don't care as much about MySQL performance as
I care
Le vendredi 23 février 2007, vous avez écrit :
> At Wed, 21 Feb 2007 05:50:48 -0500,
> Veronique & Vincent wrote:
> >
> > Hi,
> >
> > I'm currently running a 2.6.19 kernel and 2 times out of 3 the sound driver
> > fails to load hence probing me a no sound device available in KDE.
> >
> >
Patrick Ale wrote:
On 2/24/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
On 2/24/07, Michael-Luke Jones <[EMAIL PROTECTED]> wrote:
One more question regarding this, I am aware its not *really* kernel
related but answering this question now will save yourself a lot of
bogus emails from me about
Just verifying -- It's probably already fixed, but when the e820_map
routine was moved to a separate file in the 386 architecture, what
appear to be debugging messages were left "on" for display on boot.
Were(/are) these intended to be temporary?
Linux version 2.6.20 ([EMAIL PROTECTED]) (gcc
46 = /dev/ttyCPM0 PPC CPM (SCC or SMC) - port 0
...
-47 = /dev/ttyCPM5 PPC CPM (SCC or SMC) - port 5
+49 = /dev/ttyCPM5 PPC CPM (SCC or SMC) - port 5
If CPM0 is 46, then CPM5 is not 47,
Hi all,
Various hotplug packages have had trouble dealing with network
interface being renamed. I've decided to tackle this issue from two
angles :
o export ifindex to those apps, as ifindex is persistent.
o expose interface renaming as a hotplug
On Tuesday 27 February 2007, Maynard Johnson wrote:
> I have applied the "cleanup" patch that Arnd sent, but had to fix up a
> few things:
> - Bug fix: Initialize retval in spu_task_sync.c, line 95, otherwise
> OProfile this function returns non-zero and OProfile fails.
> - Remove
Andrew wrote:
I have just discovered 2.6.21-rc1 boots with
pci=noacpi ...
Try setting the resolution and frame rate, video=XXX:[EMAIL PROTECTED] or
such. Worked for me. I like pci=noacpi, though ;-)
--
Bill Davidsen <[EMAIL PROTECTED]>
"We have more to fear from the bungling of the
From: Robert Hancock <[EMAIL PROTECTED]>
Subject: Re: SMP performance degradation with sysbench
Date: Tue, 27 Feb 2007 18:20:25 -0600
Message-ID: <[EMAIL PROTECTED]>
> Hiro Yoshioka wrote:
> > Howdy,
> >
> > MySQL 5.0.26 had some scalability issues and it solved since 5.0.32
> >
On 2/26/07, Nick Piggin <[EMAIL PROTECTED]> wrote:
Rik van Riel wrote:
> Lorenzo Allegrucci wrote:
>
>> Hi lkml,
>>
>> according to the test below (sysbench) Linux seems to have scalability
>> problems beyond 8 client threads:
>> http://jeffr-tech.livejournal.com/6268.html#cutid1
>>
On Wed, Feb 28, 2007 at 12:53:14AM +0300, Oleg Nesterov wrote:
> I think it is good. Srivatsa?
Maybe additional comments on why we don't skip vfork kernel tasks may be good.
Otherwise looks ok to me. Thanks Rafael for making the changes!
--
Regards,
vatsa
-
To unsubscribe from this list: send
On Tue, 27 Feb 2007 13:22:56 + (GMT) Seetharam Dharmosoth wrote:
> Hi,
>
> I have one question regarding Crash Dump.
>
> Is Kernel-2.6.20 having the default Crash dump in main
> tree?
2.6.20 has a CRASH_DUMP config option for some processor
architectures, such as ia64, i386, x86_64,
Hi.
On Wed, 2007-02-28 at 01:08 +0100, Rafael J. Wysocki wrote:
> On Wednesday, 28 February 2007 01:01, Johannes Berg wrote:
> > On Wed, 2007-02-28 at 00:57 +0100, Rafael J. Wysocki wrote:
> >
> > > Okay, in that case I'd suggest removing create_freezeable_workqueue() and
> > > make all
Jeremy Fitzhardinge wrote:
> Ingo Molnar wrote:
>
>> why not vmalloc it on the guest side? fixmaps are bad for this purpose
>> for a general paravirt implementation, it limits the size of the shared
>> info page, etc.
>>
>
> Yes. vmalloc would have the annoying side-effect of actually
This happened on a 2.6.21rc1 kernel.
Dave
--
http://www.codemonkey.org.uk
--- Begin Message ---
On Tue, 2007-02-27 at 14:52 -0500, Adam Jackson wrote:
>
>
> Well it's at least partly Xorg's fault, but it would be helpful to
> know
> what the slow path is there; so if you do
On Tuesday 27 February 2007, Eric W. Biederman wrote:
> * Add a variation of the API in interrupt.h that uses
> "struct irq *irq" instead of "unsigned int irq"
>
> Probably replacing request_irq with irq_request or something
> trivial like that.
>
> This will need to touch all of
On Wed, 2007-02-28 at 01:05 +0100, Rafael J. Wysocki wrote:
> On Wednesday, 28 February 2007 00:12, Kristian Grønfeldt Sørensen wrote:
> > On Tue, 2007-02-27 at 23:34 +0100, Rafael J. Wysocki wrote:
> > > On Tuesday, 27 February 2007 23:23, Kristian Grønfeldt Sørensen wrote:
> > > > On Tue,
On Tue, 2007-02-27 at 23:30 +0100, Rafael J. Wysocki wrote:
> On Tuesday, 27 February 2007 23:04, Rafael J. Wysocki wrote:
> > Hi,
> >
> > On Tuesday, 27 February 2007 19:45, Kristian Grønfeldt Sørensen wrote:
> > > Hi.
> > >
> > > PROBLEM: "BUG:" when resumimg from suspend-to-ram
> > >
> >
Hiro Yoshioka wrote:
Howdy,
MySQL 5.0.26 had some scalability issues and it solved since 5.0.32
http://ossipedia.ipa.go.jp/capacity/EV0612260303/
(written in Japanese but you may read the graph. We compared
5.0.24 vs 5.0.32)
The following is oprofile data
==>
On Wednesday, 28 February 2007 01:01, Johannes Berg wrote:
> On Wed, 2007-02-28 at 00:57 +0100, Rafael J. Wysocki wrote:
>
> > Okay, in that case I'd suggest removing create_freezeable_workqueue() and
> > make all workqueues nonfreezable once again for 2.6.21 (as far as I know,
> > only
> > the
On Wednesday, 28 February 2007 00:12, Kristian Grønfeldt Sørensen wrote:
> On Tue, 2007-02-27 at 23:34 +0100, Rafael J. Wysocki wrote:
> > On Tuesday, 27 February 2007 23:23, Kristian Grønfeldt Sørensen wrote:
> > > On Tue, 2007-02-27 at 23:04 +0100, Rafael J. Wysocki wrote:
> > > > Hi,
> > > >
>
On Wed, 2007-02-28 at 00:57 +0100, Rafael J. Wysocki wrote:
> Okay, in that case I'd suggest removing create_freezeable_workqueue() and
> make all workqueues nonfreezable once again for 2.6.21 (as far as I know, only
> the two XFS workqueues are affected).
I think Nigel might object but I forgot
On Wed, 2007-02-28 at 01:00 +0100, Rafael J. Wysocki wrote:
> > > How about other kthread_stop()s ? For example,
> > > kernel/softirq.c:cpu_callback() ?
> >
> > I'd they should be affected as well.
>
> They won't be, if they have PF_NOFREEZE set.
Yup, I missed that.
johannes
signature.asc
On Wednesday, 28 February 2007 00:36, Johannes Berg wrote:
> On Wed, 2007-02-28 at 02:28 +0300, Oleg Nesterov wrote:
>
> > Ugh. I know nothing, nothing, nothing about suspend. I'll try to guess.
> >
> >Commit: ed746e3b18f4df18afa3763155972c5835f284c5
>
> > Yes? with the patch above,
On Wednesday, 28 February 2007 00:28, Oleg Nesterov wrote:
> On 02/27, Rafael J. Wysocki wrote:
> >
> > We have a problem with freezable workqueues in 2.6.21-rc1 and in -mm
> > (there are only two of them, in XFS, but still). Namely, their worker
> > threads
> > deadlock with
On Tue, Feb 27, 2007 at 03:33:34PM +0100, Jens Axboe wrote:
> It looks ok (better than end_request()), though it would still be nice
> to properly end requests. See the recent thread on the lguest block
> driver.
Hi Jens,
I read through the lguest thread and came up with the patch
below,
Hi,
2007/2/28, Rob Landley <[EMAIL PROTECTED]>:
I ran "make ARCH=x86_64 menuconfig", did a lot of editing, and saved
the .config. Then I copied that to a backup, ran "make oldconfig" on the
I'd try with "make ARCH=x86_64 oldconfig"
Gregor
-
To unsubscribe from this list: send the line
On Wed, 2007-02-28 at 02:28 +0300, Oleg Nesterov wrote:
> Ugh. I know nothing, nothing, nothing about suspend. I'll try to guess.
>
>Commit: ed746e3b18f4df18afa3763155972c5835f284c5
> Yes? with the patch above, _cpu_down() called _after_ freeze_processes() ???
perfect :)
See also my
On Tue, 27 Feb 2007 18:12:42 -0500 Rob Landley wrote:
> I ran "make ARCH=x86_64 menuconfig", did a lot of editing, and saved
> the .config. Then I copied that to a backup, ran "make oldconfig" on the
> config I'd just saved, and compared it with the backup:
>
> --- .config 2007-02-27
On 02/27, Rafael J. Wysocki wrote:
>
> We have a problem with freezable workqueues in 2.6.21-rc1 and in -mm
> (there are only two of them, in XFS, but still). Namely, their worker threads
> deadlock with workqueue_cpu_callback() that gets called during the CPU
> hotplug,
> becuase
From: Miklos Szeredi <[EMAIL PROTECTED]>
This deadlock happens, when dirty pages from one filesystem are
written back through another filesystem. It easiest to demonstrate
with fuse although it could affect looback mounts as well (see
following patches).
Let's call the filesystems A(bove) and
Apologies for the resend, lkml address got mangled...
On Tuesday 27 February 2007 19:54, Mike Galbraith wrote:
> On Tue, 2007-02-27 at 09:33 +0100, Ingo Molnar wrote:
> > * Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> > > Thomas Gleixner napisał(a):
> > > > Adrian,
> > > >
> > > > On Mon,
From: Miklos Szeredi <[EMAIL PROTECTED]>
Use wake_up_all instead of wake_up in put_reserved_req(), otherwise it
is possible that the right task is not woken up.
Also create a separate reserved_req_waitq in addition to the
blocked_waitq, since they fulfill totally separate functions.
From: Miklos Szeredi <[EMAIL PROTECTED]>
Add a new semaphore to prevent asynchronous page writeback during the
TRUNCATE request.
Using i_alloc_sem would almost work, but it has to be released before
invalidating the truncated pages, so it's easier to define a separate
one.
Signed-off-by: Miklos
From: Miklos Szeredi <[EMAIL PROTECTED]>
There's a slight problem with filesystem type representation in fuse
based filesystems.
>From the kernel's view, there are just two filesystem types: fuse and
fuseblk. From the user's view there are lots of different filesystem
types. The user is not
From: Miklos Szeredi <[EMAIL PROTECTED]>
Make lifetime of 'struct fuse_file' independent from 'struct file' by
adding a reference counter and destructor.
This will enable asynchronous page writeback, where it cannot be
guaranteed, that the file is not released while a request with this
file
From: Miklos Szeredi <[EMAIL PROTECTED]>
Other than truncate, there are two cases, when fuse tries to get rid
of cached pages:
a) in open, if KEEP_CACHE flag is not set)
b) in getattr, if file size changed spontaneously
Until now invalidate_mapping_pages() were used, which didn't get rid
of
From: Miklos Szeredi <[EMAIL PROTECTED]>
Create a function sync_sb() and export it to modules. This is the
generic interface for writing back dirty data from a single
superblock.
Signed-off-by: Miklos Szeredi <[EMAIL PROTECTED]>
---
Index: linux/fs/fs-writeback.c
From: Miklos Szeredi <[EMAIL PROTECTED]>
Implement the ->writepage address space operation. Be careful not to
block if the wbc->nonblocking flag is set.
Acquire the read-write truncation semaphore for read when allocating
the request. Use the _non_owner variants, since the semaphore is held
From: Miklos Szeredi <[EMAIL PROTECTED]>
Implement the ->writepages address space operation. This is very
similar to fuse_writepage(), but batches multiple pages into a single
request.
It reuses the fuse_fill_data structure currently used by
fuse_readpages().
Signed-off-by: Miklos Szeredi
From: Miklos Szeredi <[EMAIL PROTECTED]>
Change fuse_file_mmap() to allow shared writable mappings. Change the
->set_page_dirty address space operation to __set_page_dirty_nobuffers.
In fuse_fsync() sync the inode's dirty data.
It is important, that after all writable file are closed, no more
From: Miklos Szeredi <[EMAIL PROTECTED]>
Make per-filesystem statistics about dirty and under-writeback pages
available through the fuse control filesystem.
Signed-off-by: Miklos Szeredi <[EMAIL PROTECTED]>
---
Index: linux/fs/fuse/control.c
From: Miklos Szeredi <[EMAIL PROTECTED]>
Up to now, file writes were split into page size WRITE requests. This
is inefficient, since there are two context switches per request.
So allow bigger writes, but still do it synchronously. Asynchronous
writeback would be even better, but is very
From: Miklos Szeredi <[EMAIL PROTECTED]>
Add a per-filesystem limit for the number of dirty pages. If half the
limit is reached, background writeback is started. If the limit is
reached, then start some writeback and wait until the the number goes
below the limit again.
The dirty limit is
From: Miklos Szeredi <[EMAIL PROTECTED]>
Each WRITE request must carry a valid file descriptor. When a page is
written back from a memory mapping, the file through which the page
was dirtied is not available, so a new mechananism is needed to find a
suitable file in ->writepage(s).
A list of
From: Miklos Szeredi <[EMAIL PROTECTED]>
This patch adds a new helper function fuse_write_fill() which makes it
possible to send WRITE requests asynchronously.
A new flag for WRITE requests is also added which indicates that this
a write from the page cache, and not a "normal" file write.
From: Miklos Szeredi <[EMAIL PROTECTED]>
Needed by fuse writepage.
Signed-off-by: Miklos Szeredi <[EMAIL PROTECTED]>
---
Index: linux/include/linux/rwsem.h
===
--- linux.orig/include/linux/rwsem.h2007-02-27 14:40:55.0
From: Miklos Szeredi <[EMAIL PROTECTED]>
The function do_lo_send_aops() should call
balance_dirty_pages_ratelimited() after each page similarly to
generic_file_buffered_write().
Without this, writing the loop device directly (not through a
filesystem) is very slow, and also slows the whole
From: Miklos Szeredi <[EMAIL PROTECTED]>
This deadlock is similar to the one in balance_dirty_pages, but
instead of waiting in balance_dirty_pages after submitting a write
request, it happens during a memory allocation for filesystem B before
submitting a write request.
It is easy to reproduce
From: Miklos Szeredi <[EMAIL PROTECTED]>
Set the read and write congestion state if the request queue is close
to blocking, and clear it when it's not.
This prevents unnecessary blocking in readahead and writeback.
Signed-off-by: Miklos Szeredi <[EMAIL PROTECTED]>
---
Index:
From: Miklos Szeredi <[EMAIL PROTECTED]>
Changes:
o fix theoretical NULL pointer dereference in __mpage_writepage
o merge Andrew Morton's cleanups
Clean up code duplication between mpage_writepages() and
generic_writepages().
The new generic function, write_cache_pages() takes a function
From: Miklos Szeredi <[EMAIL PROTECTED]>
Changes:
o moved check from __fput() to remove_vma(), which is more logical
o changed set_page_dirty() to set_page_dirty_mapping in hugetlb.c
o cleaned up #ifdef CONFIG_BLOCK mess
This patch makes writing to shared memory mappings update st_ctime and
From: Miklos Szeredi <[EMAIL PROTECTED]>
Changes:
o dput already checks dentry == NULL, so remove check
from prune_one_dentry()
The time shrink_dcache_parent() takes, grows quadratically with the
depth of the tree under 'parent'. This starts to get noticable at
about 10,000.
These kinds
The first part of this series (1-7) contains miscellaneous patches,
some of which are needed for fuse writable mmap to work correctly.
Some of these are resends of patches already in -mm, with minor
updates.
The rest of the series adds shared writable mapping support to fuse,
with some write
On Tue, 2007-02-27 at 23:34 +0100, Rafael J. Wysocki wrote:
> On Tuesday, 27 February 2007 23:23, Kristian Grønfeldt Sørensen wrote:
> > On Tue, 2007-02-27 at 23:04 +0100, Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > On Tuesday, 27 February 2007 19:45, Kristian Grønfeldt Sørensen wrote:
> > > >
I ran "make ARCH=x86_64 menuconfig", did a lot of editing, and saved
the .config. Then I copied that to a backup, ran "make oldconfig" on the
config I'd just saved, and compared it with the backup:
--- .config 2007-02-27 18:10:01.0 -0500
+++ tryit 2007-02-27
On Tue, Feb 27, 2007 at 12:25:17PM -0800, Andrew Morton wrote:
> > On Sun, 25 Feb 2007 23:06:21 +0300 Oleg Nesterov <[EMAIL PROTECTED]> wrote:
> > page_lock_anon_vma() uses spin_lock() to block RCU. This doesn't work with
> > PREEMPT_RCU, we have to do rcu_read_lock() explicitely. Otherwise, it is
On Mon, 2007-02-26 at 21:32 +0100, DervishD wrote:
> Hi Antonino :)
>
> * Antonino A. Daplas <[EMAIL PROTECTED]> dixit:
> > On Mon, 2007-02-26 at 18:13 +0100, DervishD wrote:
> > That's why tdfxb limits the vyres to a maximum of 4096. As to why the
> > problem disappeared just by changing
On Tue, Feb 27, 2007 at 10:58:46PM +0100, Pavel Machek wrote:
> Hi!
>
> > > ...is it "use after free"?
> > >
> > > Greg, could we reduce verbosity of driver model? "PM: Adding info for
> > > No Bus:vcs*" is not very useful.
> >
> > Maybe for you it isn't, but then again, you did enable
> >
Russell King wrote:
On Tue, Feb 27, 2007 at 01:36:56PM -0800, Andrew Morton wrote:
On Tue, 27 Feb 2007 13:18:40 -0800 Stephen Hemminger <[EMAIL PROTECTED]> wrote:
Then we should pull the existing udivdi3 implementations?
Not much point really. Some architectures have gone and done that, but
On Tuesday, 27 February 2007 23:23, Kristian Grønfeldt Sørensen wrote:
> On Tue, 2007-02-27 at 23:04 +0100, Rafael J. Wysocki wrote:
> > Hi,
> >
> > On Tuesday, 27 February 2007 19:45, Kristian Grønfeldt Sørensen wrote:
> > > Hi.
> > >
> > > PROBLEM: "BUG:" when resumimg from suspend-to-ram
> >
On Tuesday, 27 February 2007 23:04, Rafael J. Wysocki wrote:
> Hi,
>
> On Tuesday, 27 February 2007 19:45, Kristian Grønfeldt Sørensen wrote:
> > Hi.
> >
> > PROBLEM: "BUG:" when resumimg from suspend-to-ram
> >
> > My laptop have a problem with resuming from suspend-to-ram.
> > It does
On Tue, 2007-02-27 at 23:04 +0100, Rafael J. Wysocki wrote:
> Hi,
>
> On Tuesday, 27 February 2007 19:45, Kristian Grønfeldt Sørensen wrote:
> > Hi.
> >
> > PROBLEM: "BUG:" when resumimg from suspend-to-ram
> >
> > My laptop have a problem with resuming from suspend-to-ram.
> > It does
On Tue, Feb 27, 2007 at 01:36:56PM -0800, Andrew Morton wrote:
> On Tue, 27 Feb 2007 13:18:40 -0800 Stephen Hemminger <[EMAIL PROTECTED]>
> wrote:
> > Then we should pull the existing udivdi3 implementations?
>
> Not much point really. Some architectures have gone and done that, but x86
> has
I have this message in the dmesg on a mail server running on an xfs
filesystem. It appears to have happened at some point when nfsd was
restarted, but I can't seem to convince it to reproduce.
The machine is running Gentoo's 2.6.20 kernel.
BUG: at fs/inotify.c:182 set_dentry_child_flags()
Call
1 - 100 of 726 matches
Mail list logo
