Re: O_ANY [was: Re: 'native files', 'object fingerprints' [was: sendpath()]]

2001-01-16 Thread Felix von Leitner
Thus spake Ingo Molnar ([EMAIL PROTECTED]): > if you read my (radical) proposal, the identification is based on a kernel > pointer and a 256-bit random integer. So non-negative integers are not > needed. (file-IO system-calls would be modified to detect if 'Unix file > descriptors' or pointers to

Re: O_ANY [was: Re: 'native files', 'object fingerprints' [was: sendpath()]]

2001-01-16 Thread Mitchell Blank Jr
Ingo Molnar wrote: > - probably the most radical solution is what i suggested, to completely > avoid the unique-mapping of file structures to an integer range, and use > the address of the file structure (and some cookies) as an identification. IMO... gross. We do pretty much this exact thing

Re: O_ANY [was: Re: 'native files', 'object fingerprints' [was: sendpath()]]

2001-01-16 Thread Andi Kleen
On Tue, Jan 16, 2001 at 01:04:22PM +0100, Ingo Molnar wrote: > - a less radical solution would be to still map file structures to an > integer range (file descriptors) and usage-maintain files per processes, > but relax the 'allocate first non-allocated integer in the range' rule. > I'm not sure

Re: O_ANY [was: Re: 'native files', 'object fingerprints' [was: sendpath()]]

2001-01-16 Thread Peter Samuelson
[Ingo Molnar] > - probably the most radical solution is what i suggested, to > completely avoid the unique-mapping of file structures to an integer > range, and use the address of the file structure (and some cookies) > as an identification. Careful, these must cast to non-negative integers,

Re: O_ANY [was: Re: 'native files', 'object fingerprints' [was: sendpath()]]

2001-01-16 Thread Peter Samuelson
[Ingo Molnar] - probably the most radical solution is what i suggested, to completely avoid the unique-mapping of file structures to an integer range, and use the address of the file structure (and some cookies) as an identification. Careful, these must cast to non-negative integers, without

Re: O_ANY [was: Re: 'native files', 'object fingerprints' [was: sendpath()]]

2001-01-16 Thread Andi Kleen
On Tue, Jan 16, 2001 at 01:04:22PM +0100, Ingo Molnar wrote: - a less radical solution would be to still map file structures to an integer range (file descriptors) and usage-maintain files per processes, but relax the 'allocate first non-allocated integer in the range' rule. I'm not sure

Re: O_ANY [was: Re: 'native files', 'object fingerprints' [was: sendpath()]]

2001-01-16 Thread Mitchell Blank Jr
Ingo Molnar wrote: - probably the most radical solution is what i suggested, to completely avoid the unique-mapping of file structures to an integer range, and use the address of the file structure (and some cookies) as an identification. IMO... gross. We do pretty much this exact thing in

Re: O_ANY [was: Re: 'native files', 'object fingerprints' [was: sendpath()]]

2001-01-16 Thread Felix von Leitner
Thus spake Ingo Molnar ([EMAIL PROTECTED]): if you read my (radical) proposal, the identification is based on a kernel pointer and a 256-bit random integer. So non-negative integers are not needed. (file-IO system-calls would be modified to detect if 'Unix file descriptors' or pointers to