| To: | Stephen Lord <lord@xxxxxxx> |
|---|---|
| Subject: | XFS and Kernel intregration and other things |
| From: | Shawn Starr <spstarr@xxxxxxxx> |
| Date: | 27 Jan 2002 13:49:11 -0500 |
| Cc: | Linux XFS Mailing List <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <3C543711.5030704@xxxxxxx> |
| References: | <1012101803.1045.28.camel@steelnest> <1012102374.1045.35.camel@steelnest> <3 C536F44.1020301@xxxxxxx> <20020127152120.A1490@xxxxxxxxxx> <20020127154745.A20990@xxxxxxxxxxxxx> <1012143898.923.1.camel@steelnest> <3C54352B.60505@xxxxxxx> <1012151888.988.11.camel@steelnest> <3C543711.5030704@xxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
Does anyone know when/how XFS will go into 2.4/2.5? A lot of kernel developers tell me that XFS needs to dump the pagebuf and other layers on top of the VM and VFS layers. I've gotten XFS to work with 2.4.18-pre7 w/ rml's preempt and lockbreak patch and the O(1) new scheduler + wli's patch cluster. XFS runs fine without errors. I have not seen corruption yet. I removed riel's rmap patch because it seems to break XFS somehow. rmap12a completely changes vmscan.c which blows up XFS ;/ I'm going to be using XFS's testing programs from the CVS tree and report the results. Shawn |
| Previous by Date: | Re: Linux 2.4.17-xfs vs previous XFS versions and certain non-us characters in filenames, D. Stimits |
|---|---|
| Next by Date: | Re[2]: Linux 2.4.17-xfs vs previous XFS versions and certain non-us characters in filenames, Keith Matthews |
| Previous by Thread: | Re: Linux 2.4.17-xfs vs previous XFS versions and certain non-us characters in filenames, Håkan Lindqvist |
| Next by Thread: | Re: XFS and Kernel intregration and other things, Stephen Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |