mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Schubert <bschubert@ddn.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Dharmendra Singh <dharamhans87@gmail.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	linux-fsdevel@vger.kernel.org,
	fuse-devel <fuse-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org, Dharmendra Singh <dsingh@ddn.com>,
	Horst Birthelmer <hbirthelmer@ddn.com>
Subject: Re: [PATCH v5 1/1] Allow non-extending parallel direct writes on the same file.
Date: Thu, 20 Oct 2022 16:51:55 +0200	[thread overview]
Message-ID: <14d25500-98ba-d8e7-40b2-5cc0ef1e66e3@ddn.com> (raw)
In-Reply-To: <4f0f82ff-69aa-e143-e254-f3da7ccf414d@ddn.com>

Miklos,

is there anything that speaks against getting this patch into 
linux-next? Shall I resend against v6.0? I just tested it - there is no 
merge conflict. The updated patch with benchmark results in the commit 
message is here
https://github.com/aakefbs/linux/tree/parallel-dio-write


Thanks,
Bernd

  reply	other threads:[~2022-10-20 14:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  7:10 [PATCH v5 0/1] FUSE: Allow non-extending parallel direct writes Dharmendra Singh
2022-06-17  7:10 ` [PATCH v5 1/1] Allow non-extending parallel direct writes on the same file Dharmendra Singh
2022-06-17  7:36   ` Miklos Szeredi
2022-06-17  9:25     ` Bernd Schubert
2022-06-17 12:43       ` Miklos Szeredi
2022-06-17 13:07         ` Bernd Schubert
2022-09-13  8:44         ` Bernd Schubert
2022-10-20 14:51           ` Bernd Schubert [this message]
2022-10-21  6:57           ` Miklos Szeredi
2022-10-21  9:16             ` Bernd Schubert
2022-06-18 19:07   ` Vivek Goyal

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=14d25500-98ba-d8e7-40b2-5cc0ef1e66e3@ddn.com \
    --to=bschubert@ddn.com \
    --cc=dharamhans87@gmail.com \
    --cc=dsingh@ddn.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=hbirthelmer@ddn.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=vgoyal@redhat.com \
    /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®