On 8/13/00, 1:03:38 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote regarding
Re: Definitions:
> >
> > Rik van Riel wrote:
> > comment on this. Millions of users (according to what SuSE tells me our
level of usage is in
> > Europe) are not wandering around saying, damn, I keep making reiserfs
freeze. Do you use reiserfs?
> Wrong criteria:
> The real test is
> Can XYZ evil bastard with the source code construct a non setuid
application
> that causes the absolute worst case behaviour and deadlocks or crashes
the
> machine.
> As I understand it now the answer to that is yes - for reiser, xfs and
ext3
> (in fact more so for ext3 than the others)
The current journal code limits the number of async transactions to 5, so
any given user should not be able to pin more than ~20MB of ram per FS
(each transaction is a max of 1024, 4k blocks). The admin can change
this by setting JOURNAL_NUM_BITMAPS to any number >= 2 (controls the
number of async transactions), and changing JOURNAL_MAX_BATCH to any
number larger than 256 (one way to control max blocks per transaction, it
could be set smaller, but that would be slow).
This isn't perfect, as we still might hit problems if everyone else uses
all the system ram, and reiserfs can't get blocks it needs for the
journal. But with a little work, the admin should be able to throttle
reiserfs down. Is it as solid as it could be after the changes from Rik?
No, his stuff will be very useful. But, this is still an experimental
FS...
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Aug 15 2000 - 21:00:31 EST