On 12 Mar 2001, Trond Myklebust wrote:
All that is needed is to unify all the disparate credential info we
already have at the VFS level. Just look at the ridiculous number of
different places in which we currently try to save the exact same
info: 10 fields in task structure + 2-3 fields
" " == Lever, Charles [EMAIL PROTECTED] writes:
the only thing i haven't tested is whether this change
preserves good close-to-open semantics. it looks like it
should, but i don't have an application that tests this.
Try making simple test applications that compile a file
" " == Alexander Viro [EMAIL PROTECTED] writes:
Aye. It's certainly 2.5 stuff, but I'll include that into
namespace-patch for testing. We probably need to sort the API
issues out - I suspect that net/sunrpc will cause most of the
pain and you definitely know that code
" " == Alexander Viro [EMAIL PROTECTED] writes:
Umm... Let's make it pure copy-on-write cache a-la 4.4 and if
pthreads folks need this craziness with thread-group-wide
credentials change - let them pay upon changing credentials. I
really don't see any point in
-- Forwarded Message --
Subject: Re: RFC: [PATCH] ext2 BLOCK_SIZE independence
Date: Mon, 12 Mar 2001 13:45:32 +0100
From: Daniel Phillips [EMAIL PROTECTED]
On Mon, 12 Mar 2001, Anton Altaparmakov wrote:
At 02:44 12/03/2001, Alexander Viro wrote:
On Mon, 12 Mar 2001, Anton
Andi Kleen mentioned that the ext2 part of the inode union was rather large.
So I wondered if I could chop it down a bit.
* i_osync is only referenced, never set
* i_faddr, i_frag_no, i_frag_size -- we don't support fragments.
* not_used_1 can clearly be removed.
* i_high_size is obsoleted
On Mon, 12 Mar 2001, Matthew Wilcox wrote:
Andi Kleen mentioned that the ext2 part of the inode union was rather large.
So I wondered if I could chop it down a bit.
* i_faddr, i_frag_no, i_frag_size -- we don't support fragments.
I have early alpha patches for them (ext2/UFS merge).
On Mon, 12 Mar 2001, Peter J. Braam wrote:
Hi,
We were looking at generic_file_read and generic_file_write attempting to
determine if reads can see partial writes.
Writes appear to be atomic with respect to operations that are holding
i_sem. Also, the page lock is taken and the
On Mon, 12 Mar 2001, Peter J. Braam wrote:
Hi,
We were looking at generic_file_read and generic_file_write attempting to
determine if reads can see partial writes.
Yes, reads can see partial writes.
Writes appear to be atomic with respect to operations that are holding
i_sem. Also, the
