public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Subject: Re: [PATCH 1/1] io_uring: don't scm-account for non af_unix sockets
Date: Wed, 06 Apr 2022 16:41:37 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <9c44ecf6e89d69130a8c4360cce2183ffc5ddd6f.1649277098.git.asml.silence@gmail.com>

On Wed, 6 Apr 2022 21:33:56 +0100, Pavel Begunkov wrote:
> io_uring deals with file reference loops by registering all fixed files
> in the SCM/GC infrastrucure. However, only a small subset of all file
> types can keep long-term references to other files and those that don't
> are not interesting for the garbage collector as they can't be in a
> reference loop. They neither can be directly recycled by GC nor affect
> loop searching.
> 
> [...]

Applied, thanks!

[1/1] io_uring: don't scm-account for non af_unix sockets
      commit: 181440ea22d834719489d2a33289f2834a333687

Best regards,
-- 
Jens Axboe




      reply	other threads:[~2022-04-06 22:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 20:33 [PATCH 1/1] io_uring: don't scm-account for non af_unix sockets Pavel Begunkov
2022-04-06 22:41 ` Jens Axboe [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=164928489789.13740.14903089053110765479.b4-ty@kernel.dk \
    [email protected] \
    [email protected] \
    [email protected] \
    /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