| To: | Eric Sandeen <sandeen@xxxxxxx> |
|---|---|
| Subject: | Re: XFS 1.1 and pre-emptible kernel??? |
| From: | utz lehmann <xfs@xxxxxxxxxx> |
| Date: | Mon, 15 Jul 2002 22:27:46 +0200 |
| Cc: | Mike Baptiste <mike@xxxxxxxxxxxxxxxx>, rjmx@xxxxxxxx, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <1026765251.7431.34.camel@stout.americas.sgi.com> |
| References: | <87it3hhs1o.wl@khufu.rjmx.net> <3D3330C8.7050608@thebaptistes.net> <1026765251.7431.34.camel@stout.americas.sgi.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5.1i |
Eric Sandeen [sandeen@xxxxxxx] wrote: > On Mon, 2002-07-15 at 15:30, Mike Baptiste wrote: > > > Well, I can attest that pretty much every process that exits on my > > machine generates these messages. But so far, my machine has run like a > > rock with it - so for now I'm ignoring the logs and plowing ahead ;) > > I think that the rest of RML's post said that if you were getting > 0, > then pre-empt was essentially not doing it's job. Safe, probably, but > not actually doing anything. :) So plowing ahead is fine, but your > machine might not be running the way you think it is. I can confirm this. The 2.4.18 and 1.1 patches produced tons of this error/warnings and the preempt snappies was gone (no preemption works). Using a CVS kernel is ok. I only get this warnings while unmounting on shutdown. utz |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS 1.1 and pre-emptible kernel???, Eric Sandeen |
|---|---|
| Next by Date: | Re: sysctl tuning for XFS., Austin Gonyou |
| Previous by Thread: | Re: XFS 1.1 and pre-emptible kernel???, Eric Sandeen |
| Next by Thread: | Re: XFS 1.1 and pre-emptible kernel???, Mike Baptiste |
| Indexes: | [Date] [Thread] [Top] [All Lists] |