From: David Miller <davem@davemloft.net>
To: viro@zeniv.linux.org.uk
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] sockfs: switch to ->free_inode()
Date: Mon, 08 Jul 2019 19:25:52 -0700 (PDT) [thread overview]
Message-ID: <20190708.192552.833537119648669033.davem@davemloft.net> (raw)
In-Reply-To: <20190705191322.GK17978@ZenIV.linux.org.uk>
From: Al Viro <viro@zeniv.linux.org.uk>
Date: Fri, 5 Jul 2019 20:13:22 +0100
> we do have an RCU-delayed part there already (freeing the wq),
> so it's not like the pipe situation; moreover, it might be
> worth considering coallocating wq with the rest of struct sock_alloc.
> ->sk_wq in struct sock would remain a pointer as it is, but
> the object it normally points to would be coallocated with
> struct socket...
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Applied.
prev parent reply other threads:[~2019-07-09 2:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 19:13 [PATCH] sockfs: switch to ->free_inode() Al Viro
2019-07-05 19:14 ` [PATCH] coallocate socket_wq with socket itself Al Viro
2019-07-09 2:25 ` David Miller
2019-07-09 2:25 ` David Miller [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=20190708.192552.833537119648669033.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).