It doesn't seem rate limited to me, it floods the console and log
files. If i can't tune the vm settings to decrease the likelyhood of
this error message, what can i do? Is rate limiting the error message
at scsi_merge.c a good idea?
Thanks,
Pedro
On 30 Aug 2002 at 9:18, Rik van Riel wrote:
> On Fri, 30 Aug 2002, Pedro M. Rodrigues wrote:
>
> > I do wan't to tune the vm settings, these warnings may not be
> > fatal but it's not pretty to have hundreds of those in the console
> > and log files. Bear with me on this one, but i remember doing
> > exactly that in the past, tuning /proc/sys/vm/freepages. How does
> > one acomplish that nowadays? I looked at the kernel source
> > documentation and still found references to freepages, but
> > vm/freepages doesn't exist anymore. Kernel is 2.4.18-10 from Redhat.
>
> For fundamental reasons it's always possible for non-sleeping
> allocations to fail. I think this warning just needs to be
> rate-limited, if it isn't already ...
>
> OTOH, failed allocations could serve as a hint for kswapd to
> try to keep more memory free. I should look into that for some
> next version.
>
> regards,
>
> Rik
> --
> Bravely reimplemented by the knights who say "NIH".
>
> http://www.surriel.com/ http://distro.conectiva.com/
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Aug 31 2002 - 22:00:33 EST