On 27 August 2012 09:47, Dag-Erling Smørgrav wrote:
> Eitan Adler writes:
>> "Dag-Erling Smørgrav" writes:
>> > On an amd64 system, you should just set it to 0.
>> Can we put this advice into the printf?
>
> There is no need for that, as 0 is already the default for amd64 in
> head, and I intend
Eitan Adler writes:
> "Dag-Erling Smørgrav" writes:
> > On an amd64 system, you should just set it to 0.
> Can we put this advice into the printf?
There is no need for that, as 0 is already the default for amd64 in
head, and I intend to MFC that change very soon.
DES
--
Dag-Erling Smørgrav - d
On 27 August 2012 05:50, Dag-Erling Smørgrav wrote:
> OriS writes:
>> "Dag-Erling Smørgrav" writes:
>> > On an amd64 system, you should just set it to 0.
>> Well, maybe it'd be a good idea to set it to 0 on amd64 systems for
>> amd64-RELEASE's.
Can we put this advice into the printf?
--
Eita
Christer Solskogen writes:
> Mine is 33554432 without any modifications to loader.conf on 9.1-RC1.
> Is that the default?
It is the hardcoded default for both i386 and amd64 in 9.1 and earlier
releases. I have not merged the new limits and warning code yet.
DES
--
Dag-Erling Smørgrav - d...@de
On Mon, Aug 27, 2012 at 11:50 AM, Dag-Erling Smørgrav wrote:
> OriS writes:
>> "Dag-Erling Smørgrav" writes:
>> > On an amd64 system, you should just set it to 0.
>> Well, maybe it'd be a good idea to set it to 0 on amd64 systems for
>> amd64-RELEASE's.
>
> Already done.
>
Mine is 33554432 with
OriS writes:
> "Dag-Erling Smørgrav" writes:
> > On an amd64 system, you should just set it to 0.
> Well, maybe it'd be a good idea to set it to 0 on amd64 systems for
> amd64-RELEASE's.
Already done.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
free
Yep, this also causes the warning not to be emitted at all.
Well, maybe it'd be a good idea to set it to 0 on amd64 systems for
amd64-RELEASE's.
OriS
On Mon, Aug 27, 2012 at 11:21 AM, Dag-Erling Smørgrav wrote:
> OriS writes:
> > The value of kern.maxswzone in /boot/loader.conf is:
> >
> >
OriS writes:
> The value of kern.maxswzone in /boot/loader.conf is:
>
> kern.maxswzone=201326592
On an amd64 system, you should just set it to 0.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-stable@freebsd.org mailing list
http://lists.fre
Sergey Kandaurov writes:
> Index: /usr/src/sys/vm/swap_pager.c
> ===
> --- /usr/src/sys/vm/swap_pager.c(revision 239722)
> +++ /usr/src/sys/vm/swap_pager.c(working copy)
> @@ -2135,7 +2135,7 @@ swapon_check_swzone(unsi
Yup, that seems to be the issue...
I kept bumping up the value of kern.maxswzone until the warning disappeared.
Should be incorporated into sources I guess.
Thanks! :)
Noor
On Mon, Aug 27, 2012 at 10:26 AM, Sergey Kandaurov wrote:
> On 27 August 2012 10:48, OriS wrote:
> > Hello all,
> >
> > I
On 27 August 2012 10:48, OriS wrote:
> Hello all,
>
> I have a strange warning message in dmesg:
>
> warning: total configured swap (15728640 pages) exceeds maximum
> recommended amount (22369984 pages).
> warning: increase kern.maxswzone or reduce amount of swap.
>
> (The configured pages
Hello all,
I have a strange warning message in dmesg:
warning: total configured swap (15728640 pages) exceeds maximum
recommended amount (22369984 pages).
warning: increase kern.maxswzone or reduce amount of swap.
(The configured pages are actually less than maximum)
The value of kern.m
12 matches
Mail list logo