The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	andriy.shevchenko@linux.intel.com, corbet@lwn.net,
	linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	viro@zeniv.linux.org.uk, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] relay: Remove unused relay_late_setup_files
Date: Mon, 12 May 2025 01:30:46 +0000	[thread overview]
Message-ID: <aCFPRhfxKUeRu1Qh@gallifrey> (raw)
In-Reply-To: <CAL+tcoCVjihJc=exL4hJDaLFr=CrMx=2JgYO_F_m12-LP9Lc-A@mail.gmail.com>

* Jason Xing (kerneljasonxing@gmail.com) wrote:
> Hi All,

Hi Jason,

> I noticed this patch "relay: Remove unused relay_late_setup_files"
> appears in the mm branch already[1], which I totally missed. Sorry for
> joining the party late.
> 
> I have a different opinion on this. For me, I'm very cautious about
> what those so-called legacy interfaces are and how they can work in
> different cases and what the use case might be... There are still a
> small number of out-of-tree users like me heavily relying on relayfs
> mechanism. So my humble opinion is that if you want to remove
> so-called dead code, probably clearly state why it cannot be used
> anymore in the future.

We've got lots of deadcode, why it's dead varies a lot; for example
people forgetting to clean it up after other patches etc - so this
_could_ be used but hasn't been for well over 7 years.

> Dr. David, I appreciate your patch, but please do not simply do the
> random cleanup work __here__. If you take a deep look at the relayfs,
> you may find there are other interfaces/functions no one uses in the
> kernel tree.

Actually, that was the only interface in relay that I found unused.

> I'm now checking this kind of patch in relayfs one by one to avoid
> such a thing happening. I'm trying to maintain it as much as possible
> since we internally use it in the networking area to output useful
> information in the hot paths, a little bit like blktrace. BTW, relayfs
> is really a wonderful one that helps kernel modules communicate with
> userspace very efficiently. I'm trying to revive it if I can.

If you've got a use for that function, then I'm more than happy to suggest
just dropping my patch.

However, it is a fairly chunky function that is built into distro
kernels - so I think it should have a little thought put to it.

As I say, if you are using it, it's fine by me just to drop this patch.

Dave

> [1]: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/commit/?h=mm-everything&id=46aa76118ee365c25911806e34d28fc2aa5ef997
> 
> Thanks,
> Jason
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\        dave @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  reply	other threads:[~2025-05-12  1:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12  1:12 [PATCH] relay: Remove unused relay_late_setup_files Jason Xing
2025-05-12  1:30 ` Dr. David Alan Gilbert [this message]
2025-05-12  2:22   ` Jason Xing
2025-05-12 11:50     ` Dr. David Alan Gilbert
2025-05-12 12:04       ` Jason Xing
2025-05-12  6:14 ` Andy Shevchenko
2025-05-12  6:17   ` Andy Shevchenko
2025-05-12  6:55     ` Jason Xing
2025-05-12  7:25       ` Andy Shevchenko
2025-05-12  6:53   ` Jason Xing
2025-05-12  7:21     ` Andy Shevchenko
2025-05-12  7:34       ` Jason Xing
2025-05-12 13:27       ` Jens Axboe
2025-05-12 14:55   ` Christoph Hellwig
2025-05-13  0:49     ` Jason Xing
2025-05-13  1:49       ` Jens Axboe
2025-05-13  2:17         ` Jason Xing
2025-05-13 13:26           ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2025-04-18 23:49 linux
2025-04-20 21:07 ` Andrew Morton
2025-04-23 20:12   ` Jens Axboe

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=aCFPRhfxKUeRu1Qh@gallifrey \
    --to=linux@treblig.org \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=axboe@kernel.dk \
    --cc=corbet@lwn.net \
    --cc=kerneljasonxing@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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