* David Brownell <[EMAIL PROTECTED]> wrote:
> I've been trying to make sure the x86 world could realistically switch
> to the RTC framework used by other Linux platforms, hence e.g. the
> util-unix-ng updates, but never assumed there would be no userspace
> changes. After all, userspace was u
On Wed, Jan 02, 2008 at 11:57:10AM -0800, Linus Torvalds wrote:
>
>
> On Wed, 2 Jan 2008, Matthew Wilcox wrote:
> >
> > sd_done and sr_done are called for REQ_TYPE_FS -- if the request comes
> > in through one of the SG interfaces, we call scsi_setup_blk_pc_cmnd()
> > which sets the ->done callb
* David Brownell <[EMAIL PROTECTED]> wrote:
> > shouldnt we provide a Kconfig way of replacing dev 10:135 with the
> > new driver's 254:0 device? (while keeping all the current modes of
> > operation as well, of course.)
>
> The major number 254 is not statically allocated, ISTR; that should b
On Wed, Jan 02, 2008 at 11:57:10AM -0800, Linus Torvalds wrote:
> On Wed, 2 Jan 2008, Matthew Wilcox wrote:
> >
> > sd_done and sr_done are called for REQ_TYPE_FS -- if the request comes
> > in through one of the SG interfaces, we call scsi_setup_blk_pc_cmnd()
> > which sets the ->done callback to
On Wed, 2 Jan 2008, Oliver Neukum wrote:
> Am Dienstag 01 Januar 2008 schrieb Pavel Machek:
> > Hi1
> >
> > > I would like to request a feature in the Linux kernel that would allow
> > > a user to unplug a live read-only root file system which exists on a
> > > detachable storage device such as a
* Abhishek Sagar <[EMAIL PROTECTED]> wrote:
> > > + default:
> > > + /* impossible cases */
> > > + BUG();
> >
> > I think no need to check that here.
>
> It may not get hit at runtime but is quite informative.
sidenote: please use WARN_ON(1) instead. In the case of
On Fri, 28 Dec 2007, Al Viro wrote:
> On Thu, Dec 27, 2007 at 06:19:46PM -0800, Christoph Lameter wrote:
> > nfsd4_delegations? What is this about?
>
> The random lifetimes of user-visible files you create in sysfs.
Well these are symlinks.
> > How do I scan for the symlinks in sysfs?
>
> At w
On Wednesday 02 January 2008, Alan Stern wrote:
> On Wed, 2 Jan 2008, Mike Frysinger wrote:
>
> > perhaps the code size is arguable as to whether it really matters.
> > the reason we want it is that we have a USB host controller that will
> > not work with USB hubs, so we want to make sure the sys
On Wednesday 02 January 2008, Ingo Molnar wrote:
>
> then please provide a kernel config option for the new driver to take
> over 10:135 too. There's nothing worse to the adoption of new kernel
> features necessiating user-space attention. I've got several images of
> old distros that i dont wa
On Wednesday, 2 of January 2008, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>
> > > Try to delete your fs/ directory in your output dir. Then I expect
> > > the same bug to surface again.
> >
> > It does surface indeed.
>
> could you try the patch from Sam below - do
On Mon, Dec 31, 2007 at 11:54:26AM -0800, Dave Hansen wrote:
> > Btw, I just noticed in current -mm fs_may_remount_ro() is still around
> > and not replaced by ther per-sb writers count. That surely sounds like
> > some kind of mismerge..
>
> I was actually leaving that for later. Getting rid of
On Mon, Dec 31, 2007 at 02:54:48PM -0800, Dave Hansen wrote:
> Here's one blatantly untested idea I have. The idea is to keep track if
> anyone might be writing to a mnt. We keep track on a flag in the mnt.
> When we set the flag, we increment a counter in the sb and decrement
> when the flag is
On Wed, Jan 02, 2008 at 02:18:27PM +0200, Boaz Harrosh wrote:
> > But yes, this is one of the rare cases where a typedef makes sense,
> > but ???'d call it osd_off_t or something like that.
> >
>
> You mean osd_cdb_offset_t. I thought of dropping that _t, I hate it,
> just a personal preference.
Hi Linus,
please cherrypick 35f2e577e432b28969710bc1fd4d9a4c0875f81b from
the git://computergmbh.de/linux repository from the "netfilter"
branch (or use patch below).
thanks,
Jan
==
commit 35f2e577e432b28969710bc1fd4d9a4c0875f81b
Author: Jan Engelhardt <[EMAIL PROTECTED]>
Date: Wed J
The patch below was put in 2.6.23.12 as a fix for
http://bugzilla.kernel.org/show_bug.cgi?id=9514. It apparently
does make 9514 go away, but only by coincidence. There are a
couple other ideas about fixing 9514. My proposed patch is
attached in the bugzilla.
The .12 patch reduces the number of
Erez Zadok wrote:
> Setting: ltp-full-20071031, dio01 test on ext3 with Linus's latest tree.
> Kernel w/ SMP, preemption, and lockdep configured.
This is a real lock ordering problem. Thanks for reporting it.
The updating of atime inside sys_mmap() orders the mmap_sem in the vfs
outside of the j
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> On Wednesday, 2 of January 2008, Ingo Molnar wrote:
> >
> > * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> >
> > > > Try to delete your fs/ directory in your output dir. Then I expect
> > > > the same bug to surface again.
> > >
> > > It does
On Mon, Nov 12, 2007 at 03:30:11PM +0100, [EMAIL PROTECTED] wrote:
> From: Martin Schwidefsky <[EMAIL PROTECTED]>
> Solution: The only solution I found to this dilemma is a new typedef:
> a pgtable_t. For s390 pgtable_t will be a (pte *) - to be introduced
> with a later patch. For everybody else i
On Wed, 2 Jan 2008, James Bottomley wrote:
>
> OK ... I'll revert it. However, I still think it's the wrong course of
> action, because as far as my analysis goes, this code is functionally
> equivalent to what went before with the exception that we now rely on
> the request->cmd_type informati
On Fri, 28 Dec 2007, Dhaval Giani wrote:
> we managed to get your required information. Last 10,000 lines are
> attached (The uncompressed file comes to 500 kb).
>
> Hope it helps.
Somehow the nr_pages field is truncated to 16 bit and it
seems that there are sign issues there? We are wrapping a
If create symlink on UFS2 filesystem under Linux,
it looks wrong under other OSes, because of max symlink length
field was not initialized properly, and data blocks were not
used to save short symlink names.
Signed-off-by: Evgeniy Dushistov <[EMAIL PROTECTED]>
Cc: Steven <[EMAIL PROTECTED]>
---
On Sun, 30 Dec 2007, Ingo Molnar wrote:
> so we still dont seem to understand the failure mode well enough. This
> also looks like a quite dangerous change so late in the v2.6.24 cycle.
> Does it really fix the OOM? If yes, why exactly?
Not exactly sure. I suspect that there is some memory corr
On Wed, 2 Jan 2008, Christoph Hellwig wrote:
>
> I think you misunderstood Matthew here. REQ_TYPE_BLOCK_PC is indeed
> used by any kind of SG_IO or similar passthrough no matter where it
> originates. And exactly because REQ_TYPE_BLOCK_PC are entirely passthru
> the actual driver (sd, sr or sg
On Wed, 2 Jan 2008 10:41:57 -0700
Andreas Dilger <[EMAIL PROTECTED]> wrote:
> On Jan 02, 2008 03:32 +0200, Adrian Bunk wrote:
> > It might make sense to offer ext4 in -mm and even in early -rc kernels,
> > but I've already seen people using ext4 simply because a stable kernel
> > offered it - a
On Wed, 2 Jan 2008, Torsten Kaiser wrote:
> I just tested something with vanilla 2.6.24-rc6 and had the same problem.
> Should this patch, or something similar be included for 2.6.24?
Such a patch is in Andrew's tree.
2.6.24-rc6-mm1:
tatic struct kmem_cache_node *early_kmem_cache_node_alloc(gfp
On Wed, 2 Jan 2008, Jan Engelhardt wrote:
>
> please cherrypick 35f2e577e432b28969710bc1fd4d9a4c0875f81b from
> the git://computergmbh.de/linux repository from the "netfilter"
> branch (or use patch below).
Umm. This is missing an explanation of what exactly cares.. Does it
actually fix some b
> On Wed, Jan 02, 2008 at 06:53:00PM +0100, Miklos Szeredi wrote:
> > The below patch was needed to make UML compile in latest -mm.
>
> ACK on that - I've got the same patch on its way.
>
> > But sometimes it doesn't boot and does weird things (this is a sample
> > with init=/bin/bash):
>
> > (n
On Wed, Jan 02, 2008 at 12:49:32PM -0800, Linus Torvalds wrote:
> Maybe it's not that one suspicious test. Maybe it's somethign else. But
> that commit was confirmed to break something, almost two months ago. You
> guys seem to be in denial, and saying "it didn't change anything".
>
> And no, wa
On Fri, 28 Dec 2007, Andi Kleen wrote:
> On Friday 28 December 2007 01:10:51 [EMAIL PROTECTED] wrote:
> > x86_64 provides an optimized way to determine the local per cpu area
> > offset through the pda and determines the base by accessing a remote
> > pda.
>
> And? The rationale for this patch se
Hi, sorry for delay.
On Fri, Dec 14, 2007 at 05:21:31PM +0100, Jean-Marc Saffroy wrote:
> For an embedded system, I'm currently evaluating the robustness of ufs2
> write support on Linux, and my very first test, with fsx, shows serious
> problems.
>
> My test bed is a single CPU PC with a single
On Wed, 2 Jan 2008, David Brownell wrote:
> On Wednesday 02 January 2008, Alan Stern wrote:
> > On Wed, 2 Jan 2008, Mike Frysinger wrote:
> >
> > > perhaps the code size is arguable as to whether it really matters.
> > > the reason we want it is that we have a USB host controller that will
> > >
On Sat, 29 Dec 2007, Andi Kleen wrote:
> Anyways the difference between the x86 percpu.h and the generic one is
> that x86-64 uses a short cut through the PDA to get the current cpu
> offset for the current CPU case. The generic one goes through
> smp_processor_id()->array reference instead.
No
On Sun, 30 Dec 2007, Ingo Molnar wrote:
> to get more test feedback: what would be the best way to get this tested
> in x86.git in a standalone way? Can i just pick up these 10 patches and
> remove all the non-x86 arch changes, and expect it to work - or are the
> other percpu preparatory/clean
On Tue, 1 Jan 2008, Ingo Molnar wrote:
> FYI, i tried your patchset on 2.6.24-rc6+x86.git, and randconfig testing
> found a faulty 32-bit config below - the bootup would spontaneously
> reboot shortly after hitting user-space. (which suggests a triple fault)
> No log messages on the serial cons
Bugreport regarding forcedeth driver.
When returning from suspend-to-RAM the MAC-address byteorder is
reversed. After another suspend-resume cycle the MAC-address is again
correct. This brings a great deal of pain since the NIC is assigned a
random MAC-address when it is detected as invalid.
This patch should go in immediately after:
commit 5e45efc63e33ee2bae9ff4d500b53d3bf86d2b48
Author: Roland McGrath <[EMAIL PROTECTED]>
compat_binfmt_elf
Thanks,
Roland
---
[PATCH] compat_binfmt_elf Kconfig
This adds Kconfig and Makefile bits to build fs/compat_binfmt
Hi.
Rafael J. Wysocki wrote:
> On Wednesday, 2 of January 2008, Theodore Tso wrote:
>> On Wed, Jan 02, 2008 at 10:54:18AM +1100, Nigel Cunningham wrote:
I would also like the TuxOnIce issues related to drivers, ACPI, etc. to go
to
one of the kernel-related lists, but I think linux-
The second util-linux-ng 2.13.1 release candidate is available at
ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/
(Note, 2.13.1 is stable maintenance release.)
Feedback and bug reports, as always, are welcomed.
Karel
v2.13.1-rc2 Changelog:
--
blockdev
On Jan 2, 2008 9:51 PM, Christoph Lameter <[EMAIL PROTECTED]> wrote:
> On Wed, 2 Jan 2008, Torsten Kaiser wrote:
>
> > I just tested something with vanilla 2.6.24-rc6 and had the same problem.
> > Should this patch, or something similar be included for 2.6.24?
>
> Such a patch is in Andrew's tree.
This patch replaces the earlier patch by the same title already in x86/mm:
commit a9014d2dfcb253fb3ce5f4e3318849f743b85427
Author: Roland McGrath <[EMAIL PROTECTED]>
x86 compat_binfmt_elf
It requires the new patch I just posted, titled "compat_binfmt_elf Kconfig".
T
On Jan 2, 2008 12:00 PM, Andi Kleen <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 02, 2008 at 11:43:08AM -0800, Russell Leidich wrote:
> > > > + */
> > > > + for (nb_num = 0; nb_num < num_k8_northbridges; nb_num++) {
> > > > + if ((k8_northbridges[nb_num]->device) == 0x1103)
> > > >
This replaces my earlier patch of the same title, posted with:
Subject: [PATCH -mm 18/43] powerpc compat_binfmt_elf
Date: Thu, 20 Dec 2007 03:58:16 -0800 (PST)
This requires all the powerpc patches in that series from late December and
also requires the new patch I just posted, ti
On Wed, Jan 02, 2008 at 07:26:29PM +0100, Diego Calleja wrote:
> El Wed, 2 Jan 2008 03:32:18 +0200, Adrian Bunk <[EMAIL PROTECTED]> escribió:
>
> > It might make sense to offer ext4 in -mm and even in early -rc kernels,
> > but I've already seen people using ext4 simply because a stable kernel
>
On Wed, 2 Jan 2008, Christoph Hellwig wrote:
> On Mon, Nov 12, 2007 at 03:30:11PM +0100, [EMAIL PROTECTED] wrote:
> > From: Martin Schwidefsky <[EMAIL PROTECTED]>
> > Solution: The only solution I found to this dilemma is a new typedef:
> > a pgtable_t. For s390 pgtable_t will be a (pte *) - to be
On Jan 2 2008 12:52, Linus Torvalds wrote:
>On Wed, 2 Jan 2008, Jan Engelhardt wrote:
>>
>> please cherrypick 35f2e577e432b28969710bc1fd4d9a4c0875f81b from
>> the git://computergmbh.de/linux repository from the "netfilter"
>> branch (or use patch below).
>
>Umm. This is missing an explanation of
> > Can we please just nuke CONFIG_HIGHPTE? There's only been a small
> > amount of 32bit machines with so much memory that they'd need it
> > and they can happily stay on the currently supported enterprise
> > distro releases instead of dragging this cruft around forever.
>
> And all MMU-equipp
Hi.
Pavel Machek wrote:
> Hi!
>
>> So how do you handle threads that are blocked on I/O or a lock
>> during the system freeze process, then?
> We wait until they can continue.
So if I have a process blocked on an unavilable NFS mount, I can't
suspend?
>>> That's correct, y
> Stable kernels are mainly meant for usage, not for trying stuff.
You appear to be reinventing history in your attempt to justify removing
CONFIG_EXPERIMENTAL.
> And although I see a point in perhaps shipping some not-yet-perfect
> device drivers for otherwise unsupported hardware or some
> not
On Wed, 2008-01-02 at 23:16 +0200, Adrian Bunk wrote:
> On Wed, Jan 02, 2008 at 07:26:29PM +0100, Diego Calleja wrote:
> > El Wed, 2 Jan 2008 03:32:18 +0200, Adrian Bunk <[EMAIL PROTECTED]> escribió:
> >
> > > It might make sense to offer ext4 in -mm and even in early -rc kernels,
> > > but I've
On Jan 2, 2008 10:12 PM, Russell Leidich <[EMAIL PROTECTED]> wrote:
> On Jan 2, 2008 12:00 PM, Andi Kleen <[EMAIL PROTECTED]> wrote:
> > On Wed, Jan 02, 2008 at 11:43:08AM -0800, Russell Leidich wrote:
> > > likelihood, will extend to some future CPUs). Indeed, as far as my
> > > testing has deter
* Christoph Lameter <[EMAIL PROTECTED]> wrote:
> On Tue, 1 Jan 2008, Ingo Molnar wrote:
>
> > FYI, i tried your patchset on 2.6.24-rc6+x86.git, and randconfig testing
> > found a faulty 32-bit config below - the bootup would spontaneously
> > reboot shortly after hitting user-space. (which sug
On Wed, 2 Jan 2008, Jan Engelhardt wrote:
>
> A cleanup. Or perhaps a precautionary change, should unsigned long
> long ever become something that is not 64-bit. It was intended for
> 2.6.25 actually. You don't take patches this early, do you?
Yeah, no, I don't take patches early. I've considere
On Jan 2 2008 13:42, Linus Torvalds wrote:
>On Wed, 2 Jan 2008, Jan Engelhardt wrote:
>>
>> A cleanup. Or perhaps a precautionary change, should unsigned long
>> long ever become something that is not 64-bit. It was intended for
>> 2.6.25 actually. You don't take patches this early, do you?
>
>Yea
Hi Martin.
Martin Steigerwald wrote:
> Am Mittwoch 02 Januar 2008 schrieb Nigel Cunningham:
>> Hi.
>
> Hi,
>
>> Rafael J. Wysocki wrote:
>>> On Wednesday, 2 of January 2008, Theodore Tso wrote:
On Wed, Jan 02, 2008 at 10:54:18AM +1100, Nigel Cunningham
wrote:
>> I would also like t
Hi,
On Wed, Jan 02, 2008 at 10:04:49PM +0100, Richard Jonsson wrote:
> Bugreport regarding forcedeth driver.
>
> When returning from suspend-to-RAM the MAC-address byteorder is reversed.
> After another suspend-resume cycle the MAC-address is again correct. This
> brings a great deal of pain sin
On Jan 2, 2008 1:33 PM, Torsten Kaiser <[EMAIL PROTECTED]> wrote:
> On Jan 2, 2008 10:12 PM, Russell Leidich <[EMAIL PROTECTED]> wrote:
> > On Jan 2, 2008 12:00 PM, Andi Kleen <[EMAIL PROTECTED]> wrote:
> > > On Wed, Jan 02, 2008 at 11:43:08AM -0800, Russell Leidich wrote:
> > > > likelihood, will
One of the benefits of the r/o bind mount patches is that they
make it explicit when a write to a superblock might occur.
We currently search sb->s_files when remounting rw->ro to look
for writable files. But, that search is not comprehensive, and
it is racy. This replaces that search.
The idea
> > Isn't CONFIG_EXPERIMENTAL enough?
>
> Most people and all distributions use CONFIG_EXPERIMENTAL=y simply
> because too many options (including options required for hardware
> support) depend on it.
Maybe I'm wrong, but I think most people use the distro-provided
precompiled kernels. This is
> Thanks. My code doesn't support these CPUs because their northbridge
> IDs are not 0x1203.
Sure, but do they have the crippling erratum too?
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at ht
On Wed, Jan 02, 2008 at 07:29:59PM +0100, Torsten Kaiser wrote:
>
> Vanilla 2.6.24-rc6 seems stable. I did not see any crash or warnings.
OK that's great. The next step would be to try excluding specific git
trees from mm to see if they make a difference.
The two specific trees of interest would
On Wed, Jan 02, 2008 at 01:08:31PM -0800, Roland McGrath wrote:
> This patch should go in immediately after:
>
> commit 5e45efc63e33ee2bae9ff4d500b53d3bf86d2b48
> Author: Roland McGrath <[EMAIL PROTECTED]>
>
> compat_binfmt_elf
>
> Thanks,
> Roland
>
> ---
> [PATCH] compat
Just traced it again on my system: It is okay for the number of pages on
the quicklist to reach the high count that we see (although the 16 bit
limits are weird. You have around 4GB of memory in the system?). Up to
1/16th of free memory of a node can be allocated for quicklists (this
allows the
On Thu, Jan 03, 2008 at 08:51:54AM +1100, Herbert Xu wrote:
> On Wed, Jan 02, 2008 at 07:29:59PM +0100, Torsten Kaiser wrote:
> >
> > Vanilla 2.6.24-rc6 seems stable. I did not see any crash or warnings.
>
> OK that's great. The next step would be to try excluding specific git
> trees from mm to
Hi Abhishek,
Abhishek Sagar wrote:
> On 1/2/08, Masami Hiramatsu <[EMAIL PROTECTED]> wrote:
>> I think setup_singlestep() in your first patch is better, because it avoided
>> code duplication(*).
>
> Will retain it then.
Thank you very much.
>>> static int __kprobes reenter_kprobe(struct kprob
* Roland McGrath <[EMAIL PROTECTED]> wrote:
> This patch should go in immediately after:
>
> commit 5e45efc63e33ee2bae9ff4d500b53d3bf86d2b48
> Author: Roland McGrath <[EMAIL PROTECTED]>
>
> compat_binfmt_elf
>
> Thanks,
> Roland
>
> ---
> [PATCH] compat_binfmt_elf Kconfi
* Roland McGrath <[EMAIL PROTECTED]> wrote:
> This patch replaces the earlier patch by the same title already in
> x86/mm:
>
> commit a9014d2dfcb253fb3ce5f4e3318849f743b85427
> Author: Roland McGrath <[EMAIL PROTECTED]>
>
> x86 compat_binfmt_elf
>
> It requires the new p
On Wed, Jan 02, 2008 at 10:53:11PM +0100, Sam Ravnborg wrote:
> On Wed, Jan 02, 2008 at 01:08:31PM -0800, Roland McGrath wrote:
> > This patch should go in immediately after:
> >
> > commit 5e45efc63e33ee2bae9ff4d500b53d3bf86d2b48
> > Author: Roland McGrath <[EMAIL PROTECTED]>
> >
> >
On Wednesday, 2 of January 2008, Nigel Cunningham wrote:
> Hi.
>
> Pavel Machek wrote:
> > Hi!
> >
> >> So how do you handle threads that are blocked on I/O or a lock
> >> during the system freeze process, then?
> > We wait until they can continue.
> So if I have a process bloc
On Wed, Jan 02, 2008 at 09:52:41PM +0100, Miklos Szeredi wrote:
> 32bit UML, 64bit host, config attached.
Hadn't tried that, but that works here too.
I'll see if your config reproduces it.
> Can't reproduce with plain -rc6.
Feel like bisecting -mm1?
Jeff
--
Wo
I have no opinions about the config symbol names. Among the existing
precedents for internal/descriptionless symbols I find more not using the
HAVE_ prefix than those using it. The patch versions I've sent now work
fine, fix the parallel build problem people were seeing, and AFAICT follow
the sty
On Jan 2, 2008 1:54 PM, Andi Kleen <[EMAIL PROTECTED]> wrote:
> > Thanks. My code doesn't support these CPUs because their northbridge
> > IDs are not 0x1203.
>
> Sure, but do they have the crippling erratum too?
We don't seem to have erratum documentation on this chip, so I can't
confirm one way
On Wednesday 02 January 2008, Matt Domsch wrote:
> On Tue, Jan 01, 2008 at 09:32:36PM -0500, Jon Masters wrote:
> > On Tue, 2008-01-01 at 19:33 +0100, Bartlomiej Zolnierkiewicz wrote:
> >
> > > On the second thought: maybe we will be better off with limiting
> > > MODULE_VERSION() to the device dr
On Fri, Dec 28, 2007 at 05:22:51PM +0100, Jochen Friedrich wrote:
> This patch adds device tree source, default config and setup code for
> DBox2 devices.
[snip]
> +++ b/arch/powerpc/boot/dts/dbox2.dts
> @@ -0,0 +1,251 @@
> +/*
> + * DBOX2 Device Tree Source
> + *
> + * Copyright 2007 Jochen Fried
On Wed, Jan 02, 2008 at 11:45:17PM +0100, Bartlomiej Zolnierkiewicz wrote:
> Unfortunately 'srcversion' is set only if MODULE_VERSION() is used... :(
or CONFIG_MODULE_SRCVERSION_ALL=y. I see Fedora doesn't use that :-(
but Ubuntu, openSUSE do.
/me files a change request...
--
Matt Domsch
Linux
On 1/3/08, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> > 2.6.25 actually. You don't take patches this early, do you?
>
> Yeah, no, I don't take patches early. I've considered setting up another
> branch for early patches, but decided that I'm (a) lazy and (b) better off
> encouraging people in the
Adrian Bunk wrote:
> Most people and all distributions use CONFIG_EXPERIMENTAL=y simply
> because too many options (including options required for hardware
> support) depend on it.
>
> Compare e.g.:
> - "Marvell SATA support (HIGHLY EXPERIMENTAL)"
> - "Provide NFSv4 client support (EXPERIMENTAL)
> could we perhaps just replace it with a tty_mutex? (possibly a recursive
> one) I suspect by now most of the BKL dependencies there have become
> local to the tty code? Or are there deep VFS dependencies as well? (if
> yes, what type of dependencies?)
The big problem is that nobody actually k
On Wed, 2008-01-02 at 11:35 -0800, Linus Torvalds wrote:
>
> On Wed, 2 Jan 2008, Pekka Enberg wrote:
> >
> > I already sent the remaining bits to Linus but this looks much
> > cleaner. Thanks Hugh!
> >
> > Acked-by: Pekka Enberg <[EMAIL PROTECTED]>
>
> Actually, I'd much rather just do this in
On Sat, 17 Nov 2007 21:51:25 +0100 Andreas Mohr wrote:
> Make the patch-kernel shell script sufficiently compatible with POSIX
> shells,
> i.e., remove bashisms from scripts/patch-kernel.
> This means that it now also works on dash 0.5.3-5
> and still works on bash 3.1dfsg-8.
>
> Full changelog:
On Wednesday 02 January 2008 22:13:52 Tejun Heo wrote:
> Tejun Heo wrote:
> > Tejun Heo wrote:
> >> Kbuild now generates and installs modules.order along with modules.
> >> This patch updates depmod such that it sorts module list according to
> >> the file before generating output files. Modules w
+ lts' convert anon_vma list lock to reader/write lock patch
+ Nick Piggin's move and rework isolate_lru_page() patch
Free swap cache entries when swapping in pages if vm_swap_full()
[swap space > 1/2 used?]. Uses new pagevec to reduce pressure
on locks.
Signed-off-by: Rik van Riel <[EMAIL PROTE
V1 -> V2 [lts]:
+ fix botched merge -- add back "get_page_unless_zero()"
From: Nick Piggin <[EMAIL PROTECTED]>
To: Linux Memory Management <[EMAIL PROTECTED]>
Subject: [patch 1/4] mm: move and rework isolate_lru_page
Date: Mon, 12 Mar 2007 07:38:44 +0100 (CET)
isolate_lru_page logically
Define page_file_cache() function to answer the question:
is page backed by a file?
Originally part of Rik van Riel's split-lru patch. Extracted
to make available for other, independent reclaim patches.
Moved inline function to linux/mm_inline.h where it will
be needed by subsequent "spl
Debug whether we end up classifying the wrong pages as
filesystem backed. This has not triggered in stress
tests on my system, but who knows...
DEBUGGING ONLY: NOT FOR UPSTREAM MERGE
Signed-off-by: Rik van Riel <[EMAIL PROTECTED]>
Index: linux-2.6.24-rc6-mm1/include/linux/mm_inline.h
==
V1 -> V2 [lts]:
+ Remove extraneous __dec_zone_state(zone, NR_ACTIVE) pointed
out by Mel G.
>From [EMAIL PROTECTED] Wed Aug 29 11:39:51 2007
Currently we are defining explicit variables for the inactive
and active list. An indexed array can be more generic and avoid
repeating similar code in s
Swapin_readahead can read in a lot of data that the processes in
memory never need. Adding swap cache pages to the inactive list
prevents them from putting too much pressure on the working set.
This has the potential to help the programs that are already in
memory, but it could also be a disadvan
We avoid evicting and scanning anonymous pages for the most part, but
under some workloads we can end up with most of memory filled with
anonymous pages. At that point, we suddenly need to clear the referenced
bits on all of memory, which can take ages on very large memory systems.
We can reduce
Update the split anon & file LRU code to deal with the recent
memory controller changes.
Signed-off-by: Rik van Riel <[EMAIL PROTECTED]>
Index: linux-2.6.24-rc6-mm1/include/linux/memcontrol.h
===
--- linux-2.6.24-rc6-mm1.orig/include
V2 -> V3:
+ rebase to 23-mm1 atop RvR's split LRU series
New in V2
This patch adds a function to scan individual or all zones' noreclaim
lists and move any pages that have become reclaimable onto the respective
zone's inactive list, where shrink_inactive_list() will deal with them.
This replaces
V1 -> V3:
+ rebase to 23-mm1 atop RvR's split LRU series
+ define NR_NORECLAIM and LRU_NORECLAIM to avoid errors when not
configured.
V1 -> V2:
+ handle review comments -- various typos and errors.
+ extract "putback_all_noreclaim_pages()" into a separate patch
and rework as "scan_all_zones
V2 -> V3:
+ rebase to 23-mm1 atop RvR's split LRU series
V1 -> V2:
no changes
Report non-reclaimable pages per zone and system wide.
Note: may want to track/report some specific reasons for
nonreclaimability for deciding when to splice the noreclaim
lists back to the normal lru. That
On large memory systems, the VM can spend way too much time scanning
through pages that it cannot (or should not) evict from memory. Not
only does it use up CPU time, but it also provokes lock contention
and can leave large systems under memory presure in a catatonic state.
Against 2.6.24-rc6-mm1
V2 -> V3:
+ rebase to 23-mm1 atop RvR's split LRU series.
+ Use scan_mapping_noreclaim_page() on unlock. See below.
V1 -> V2:
+ modify to use reworked 'scan_all_zones_noreclaim_pages()'
See 'TODO' below - still pending.
While working with Nick Piggin's mlock patches, I noticed that
shmem seg
V3 -> V4:
+ drivers/block/rd.c was replaced by brd.c in 24-rc4-mm1.
Update patch to add brd_open() to mark mapping as nonreclaimable
V2 -> V3:
+ rebase to 23-mm1 atop RvR's split LRU series [no changes]
V1 -> V2:
+ add ramfs pages to this class of non-reclaimable pages by
marking ramfs add
V2 -> V3:
+ rebase to 23-mm1 atop RvR's split lru series
+ fix definitions of NR_MLOCK to fix build errors when not configured.
V1 -> V2:
+ new in V2 -- pulled in & reworked from Nick's previous series
From: Nick Piggin <[EMAIL PROTECTED]>
To: Linux Memory Management <[EMAIL PROTECTED]>
Cc
V2 -> V3:
+ rebase to 23-mm1 atop RvR's split lru series [no changes]
V1 -> V2:
+ modified mmap.c:mmap_region() to return error if mlock_vma_pages_range()
does. This can only occur if the vma gets removed/changed while
we're switching mmap_sem lock modes. Most callers don't care, but
V2 -> V3:
+ rebase to 23-mm1 atop RvR's split lru series [no change]
+ fix function return types [void -> int] to fix build when
not configured.
New in V2.
We need to hold the mmap_sem for write to initiatate mlock()/munlock()
because we may need to merge/split vmas. However, this can lead to
V2 -> V3:
+ rebase to 23-mm1 atop RvR's split lru series
+ fix page flags macros for *PageMlocked() when not configured.
+ ensure lru_add_drain_all() runs on all cpus when NORECLIM_MLOCK
configured. Was just for NUMA.
V1 -> V2:
+ moved this patch [and related patches] up to right after
ramdis
V2 -> V3:
+ rebase to 23-mm1 atop RvR's split lru series.
V1 -> V2:
+ no changes
Optional part of "noreclaim infrastructure"
In the fault paths that install new anonymous pages, check whether
the page is reclaimable or not using lru_cache_add_active_or_noreclaim().
If the page is reclaimable, j
> The software definitely provides that guarantee for all NCQ-capable
> controllers.
>
Well if that's not it, it must be some problem entering ADMA legacy
mode. Here's what the Windows driver does:
ADMACtrl.aGO = 0
ADMACtrl.aEIEN = 0
poll {
until ADMAStatus.aLGCY = 1 || timeout
}
--
201 - 300 of 433 matches
Mail list logo
