| To: | Andi Kleen <ak@xxxxxxx> |
|---|---|
| Subject: | Re: xfsdump safe? |
| From: | ivanr@xxxxxxxxxxxxxxxxx (Ivan Rayner) |
| Date: | Fri, 11 May 2001 22:31:46 +1000 |
| Cc: | <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <20010511122945.A5907@gruyere.muc.suse.de> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Fri, 11 May 2001, Andi Kleen wrote: > Regarding xfsdump: > > The qlock functions seem to be dummied out (inside #ifdef HIDDEN), but > it still seems to create threads in some circumstances, which probably need > locking. Is it really safe to use? I think you'll find that the linux version of xfsdump runs in single threaded mode. This is controlled by the 'miniroot' flag which is set to true on Linux - the key bits are around line 604 in cmd/xfsdump/common/main.c. Ivan -- Ivan Rayner ivanr@xxxxxxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | xfsdump safe?, Andi Kleen |
|---|---|
| Next by Date: | Re: xfsdump safe?, Andi Kleen |
| Previous by Thread: | xfsdump safe?, Andi Kleen |
| Next by Thread: | Re: xfsdump safe?, Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |