From: Eric Dumazet <edumazet@google.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Arjun Roy <arjunroy.kdev@gmail.com>,
netdev@vger.kernel.org, arjunroy@google.com, soheil@google.com,
kuba@kernel.org, akpm@linux-foundation.org, dsahern@kernel.org,
davem@davemloft.net, linux-mm@kvack.org, pabeni@redhat.com
Subject: Re: [net-next,v2] tcp: Use per-vma locking for receive zerocopy
Date: Fri, 7 Jul 2023 17:44:44 +0200 [thread overview]
Message-ID: <CANn89iK3WkWZPJqD2=bVczPJ615zL1HHuDQ1VDXyw8AB2hyeJQ@mail.gmail.com> (raw)
In-Reply-To: <ZKcZZPB7jaDlasdR@casper.infradead.org>
On Thu, Jul 6, 2023 at 9:43 PM Matthew Wilcox <willy@infradead.org> wrote:
>
> On Fri, Jun 16, 2023 at 12:34:27PM -0700, Arjun Roy wrote:
> > However, with per-vma locking, both of these problems can be avoided.
>
> I appreciate your enthusiasm for this. However, applying this patch
> completely wrecks my patch series to push per-vma locking down for
> file-backed mappings. It would be helpful if we can back this out
> for now and then apply it after that patch series.
>
> Would it make life hard for this patch to go through the mm tree?
>
No worries, can you send a formal revert then ?
(With some details, because I do not see why you can not simply add
the revert in front of your series ?)
Thanks.
prev parent reply other threads:[~2023-07-07 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 19:34 Arjun Roy
2023-06-18 10:20 ` patchwork-bot+netdevbpf
2023-07-06 19:43 ` Matthew Wilcox
2023-07-07 15:44 ` Eric Dumazet [this message]
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='CANn89iK3WkWZPJqD2=bVczPJ615zL1HHuDQ1VDXyw8AB2hyeJQ@mail.gmail.com' \
--to=edumazet@google.com \
--cc=akpm@linux-foundation.org \
--cc=arjunroy.kdev@gmail.com \
--cc=arjunroy@google.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=soheil@google.com \
--cc=willy@infradead.org \
/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