Messages in this thread | | | Subject | Re: [PATCH] s390: Hypervisor File System | From | Michael Holzheu <> | Date | Wed, 3 May 2006 17:22:41 +0200 |
| |
mschwid2@de.ltcfwd.linux.ibm.com wrote on 05/03/2006 04:58:06 PM: > On Wed, 2006-05-03 at 16:23 +0200, Michael Holzheu wrote: > > mschwid2@de.ltcfwd.linux.ibm.com wrote on 05/03/2006 04:17:40 PM: > > > And the user space then uses the parser only? Is now the parser > > > interface the "ABI" or the kernel interface that is in turn used by the > > > parser? And what happens if somebody comes up with a "better" parser > > > that does things subtly different? > > > > The ABI is not defined by the Parser. You have to specify the > > tag language, which is part of the ABI. Any parser, which is comliant > > to the specification of the tag language can be used. > > Optimist.
One very last comment: I think for our problem to ensure consitency of hypervisor data, when an application always wants to get the complete set of information, the "one file" solution with a fully specified ASCII tag language format looks for me to be the easiest way to implement our solution. And I think, if one decides to use one file to provide all the information, it is better to have a standard data format than always invent new formats. And to use a standard ASCII format is in my eyes also better than to have a binary interface.
If everybody says, that it is in principal not a good idea to use one file, than a snapshot mechanism for filesystems is probably go good method to provide consitency. And this is definitely not my decission...
Michael
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |