ixt3
Hello, http://www.cs.wisc.edu/adsl/Publications/iron-sosp05.pdf I think I got this link from OLS papers or from fs workshop ... and I really like what it says. How many of ixt3 features are going to be implemented in ext4? -- Jure Pečar http://jure.pecar.org - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: ixt3
On Oct 17, 2006 10:36 +0200, Jure Pečar wrote: http://www.cs.wisc.edu/adsl/Publications/iron-sosp05.pdf I think I got this link from OLS papers or from fs workshop ... and I really like what it says. How many of ixt3 features are going to be implemented in ext4? None, yet. The journal checksum code has been brought into a basically ready-to-go state, and there is also work to add checksums to the group descriptors, so there is some chance that this will be added before ext4 is declared closed. Nothing done yet to checksum inodes, superblock, file index or extent blocks. None of the retry code has been looked at. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: ixt3
On Oct 17, 2006 11:06 +0200, Jure Pečar wrote: On Tue, 17 Oct 2006 02:51:30 -0600 Andreas Dilger [EMAIL PROTECTED] wrote: None of the retry code has been looked at. This is what I'm mostly interested in ... predictable, well behaving and tested error handling recovery. Is ext4 going to be any better here than ext3? Not unless someone massages the ixt3 code into a form usable in the kernel. I'd suggest you contact the authors if you are interested in doing this work. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: CFP: Linux 2007 File System IO Workshop
--- James Bottomley [EMAIL PROTECTED] wrote: You can submit it as your position paper, certainly. It is not a position paper. There is too much SCSI Architecture Model (SAM) in it. But from linux-scsi point of view I guess it is. However, the object of this event is not to collect a list of papers to be presented: it's not a conference with hundreds of attendees (if you want to present to an audience, you should submit to FAST, which is such a conference, with which we're co-located). It's a roundtable type discussion with 20-25 people in the field; plus some plenary sessions to get input and ideas from people working on the filesystem layer. The object is to stimulate discussion of important issues (which may be guided by papers or other materials). The position paper thing is only to ensure people actually have things they want to discuss (and to allow the programme committee to pick the attendees if there would be too many). Ok, so this is targeted at the same 20-25 Linux people who attended the Vancouver Storage summit and you're just using FAST to co-locate. I incorrectly assumed that this was targeted at storage professionals not necessarily Linux related, but with Linux exposure so as to hear new ideas and pathways. I also missed to see the by-invitation clause at the top. Thanks for the explanation! Luben - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
