From: Eric BEGOT <eric_begot@yahoo.fr>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-mm1
Date: Mon, 21 Jun 2004 13:48:00 +0200 [thread overview]
Message-ID: <40D6CAF0.2020402@yahoo.fr> (raw)
In-Reply-To: <20040620174632.74e08e09.akpm@osdl.org>
Andrew Morton wrote:
>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7/2.6.7-mm1/
>
>
>- Added a new vm tunable: /proc/sys/vm/vfs-cache-pressure.
>
> This allows tuning of the kernel's preference for reclaiming VFS caches
> versus pagecache.
>
> vfs-cache-pressure=0: dentry and inode caches aren't reclaimed at all
> vfs-cache-pressure=100: default - current behaviour
> vfs-cache-pressure > 100: reclaim the VFS caches harder.
>
> It seems that large values of vfs-cache-pressure are needed to make much
> difference: 1000 or more.
>
>- Under some circumstances the current page reclaim code can hold
> interrupts off for a long time. That is fixed here.
>
>- I went through and dropped a bunch of patches which don't seem to be very
> useful now - mainly debug stuff.
>
>- Various driver updates and random fixes
>
>
>
I can't compile 2.6.7-mm1. here are the errors :
CC security/selinux/hooks.o
security/selinux/hooks.c:4129: error: `selinux_netlink_send' undeclared here (not in a function)
security/selinux/hooks.c:4129: error: initializer element is not constant
security/selinux/hooks.c:4129: error: (near initialization for `selinux_ops.netlink_send')
security/selinux/hooks.c:4130: error: `selinux_netlink_recv' undeclared here (not in a function)
security/selinux/hooks.c:4130: error: initializer element is not constant
security/selinux/hooks.c:4130: error: (near initialization for `selinux_ops.netlink_recv')
make[2]: *** [security/selinux/hooks.o] Error 1
make[1]: *** [security/selinux] Error 2
make: *** [security] Error 2
With the same config, the 2.6.7 compiles perfectly. I join my .config.
Regards
next prev parent reply other threads:[~2004-06-21 11:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 0:46 2.6.7-mm1 Andrew Morton
2004-06-21 1:40 ` 2.6.7-mm1: empty help text for FB_RIVA_I2C Adrian Bunk
2004-06-21 7:38 ` Antonino A. Daplas
2004-06-21 1:43 ` [patch] 2.6.7-mm1: R8169_NAPI help text Adrian Bunk
2004-06-21 1:55 ` [patch] 2.6.7-mm1: drivers/scsi/hosts.h -> scsi/scsi_host.h Adrian Bunk
2004-06-22 3:48 ` Jeff Garzik
2004-06-21 2:04 ` 2.6.7-mm1 Adrian Bunk
2004-06-22 5:33 ` 2.6.7-mm1 Sam Ravnborg
2004-07-17 20:46 ` [2.6 patch] move STANDALONE to drivers/base/Kconfig Adrian Bunk
2004-06-21 2:06 ` 2.6.7-mm1 linker trouble with CONFIG_FB_RIVA_I2C=y and modular I2C Matthias Andree
2004-06-21 15:29 ` [patch] " Adrian Bunk
2004-06-22 15:11 ` Matthias Andree
2004-06-21 10:48 ` 2.6.7-mm1 Dominik Karall
2004-06-21 11:00 ` 2.6.7-mm1 Andrew Morton
2004-06-21 11:43 ` 2.6.7-mm1 Dominik Karall
2004-06-23 7:28 ` 2.6.7-mm1 Daniele Venzano
2004-06-21 11:48 ` Eric BEGOT [this message]
2004-06-21 14:25 ` 2.6.7-mm1 James Morris
2004-06-21 14:38 ` 2.6.7-mm1 Eric BEGOT
2004-06-22 0:15 ` 2.6.7-mm1 Adrian Bunk
2004-06-21 14:32 ` 2.6.7-mm1 (compile stats) John Cherry
2004-06-21 23:05 ` 2.6.7-mm1 I/O regression ? FabF
2004-06-21 23:18 ` FabF
-- strict thread matches above, loose matches on Subject: below --
2004-06-21 19:57 2.6.7-mm1 Luca Risolia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40D6CAF0.2020402@yahoo.fr \
--to=eric_begot@yahoo.fr \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.