From: Bernd Schubert <bschubert@ddn.com>
To: Miklos Szeredi <miklos@szeredi.hu>,
Dharmendra Hans <dharamhans87@gmail.com>
Cc: linux-fsdevel@vger.kernel.org,
fuse-devel <fuse-devel@lists.sourceforge.net>,
linux-kernel@vger.kernel.org, Dharmendra Singh <dsingh@ddn.com>
Subject: Re: [PATCH 1/1] FUSE: Allow parallel direct writes on the same file
Date: Fri, 22 Apr 2022 17:20:11 +0200 [thread overview]
Message-ID: <2c8e61de-54da-44da-3a7b-b95eabfb29f2@ddn.com> (raw)
In-Reply-To: <CAJfpegsZF4D-sshMK0C=jSECskyQRAgA_1hKD9ytsHKvmXoBeA@mail.gmail.com>
On 4/22/22 16:48, Miklos Szeredi wrote:
> On Fri, 22 Apr 2022 at 16:30, Dharmendra Hans <dharamhans87@gmail.com> wrote:
>>
>> On Thu, Apr 21, 2022 at 8:52 PM Miklos Szeredi <miklos@szeredi.hu> wrote:
>>>
>>> On Fri, 8 Apr 2022 at 08:18, Dharmendra Singh <dharamhans87@gmail.com> 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
next prev parent reply other threads:[~2022-04-22 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 6:18 [PATCH 0/1] FUSE: Parallel " Dharmendra Singh
2022-04-08 6:18 ` [PATCH 1/1] FUSE: Allow parallel " Dharmendra Singh
2022-04-21 15:22 ` Miklos Szeredi
2022-04-22 14:30 ` Dharmendra Hans
2022-04-22 14:48 ` Miklos Szeredi
2022-04-22 15:20 ` Bernd Schubert [this message]
2022-04-25 8:40 ` Miklos Szeredi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2c8e61de-54da-44da-3a7b-b95eabfb29f2@ddn.com \
--to=bschubert@ddn.com \
--cc=dharamhans87@gmail.com \
--cc=dsingh@ddn.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®