On 4/22/22 16:48, Miklos Szeredi wrote:
On Fri, 22 Apr 2022 at 16:30, Dharmendra Hans <dharamhans87@xxxxxxxxx> wrote:
On Thu, Apr 21, 2022 at 8:52 PM Miklos Szeredi <miklos@xxxxxxxxxx> wrote:
On Fri, 8 Apr 2022 at 08:18, Dharmendra Singh <dharamhans87@xxxxxxxxx> wrote:
That's true, but I still worry... Does your workload include
non-append extending writes? Seems to me making those run in parallel
is asking for trouble.
Our main use case is MPIIO for now and I don't think it first sets the
file size and would then write to these sparse files. Fixing all the
different MPI implementations including closed source stacks is probably
out of question.
Given that MPIIO also supports direct calls into its stack we also do
support that for some MPIs, but not all stacks. Direct calls bypassing
the vfs also haas it's own issues, including security. So it would be
really great if we could find a way to avoid the inode lock.
Would you mind to share what you worry about in detail?
If we agreed, I would be sending the updated patch shortly.
(Also please take a look on other patches raised by me for atomic-open, these
patches are pending since couple of weeks)
I'm looking at that currently.
Thank you! There are two more optimizations in the same area, but these
require VFS changes - let's first get the 'easy' things done...
Thanks,
Bernd
