linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	linux-kernel@vger.kernel.org, pmladek@suse.com,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v5 27/32] PCI/P2PDMA: Convert to printbuf
Date: Tue, 9 Aug 2022 01:00:44 -0700	[thread overview]
Message-ID: <YvIULAsLGMNVdPek@infradead.org> (raw)
In-Reply-To: <20220809020734.GA1260912@bhelgaas>

On Mon, Aug 08, 2022 at 09:07:34PM -0500, Bjorn Helgaas wrote:
> This doesn't tell me what the advantage of this patch is, since I
> don't think *this* patch uses heap allocation.
> 
> As far as I can tell, this particular patch doesn't improve safety or
> readability, so "convert X to Y even though we don't use any fancy Y
> features" is a pointless message.
> 
> But if printbufs are better than seq_buf overall, and converting this
> gets us closer to the goal of removing seq_buf completely, that's a
> perfectly acceptable reason.  Just say that.

Which still brings me back to a point made long time ago:  Why are
we doing the renaming to start with?  Add the new functionality and
or changes to seq_buf gradually instead of doing a tree wide sweep.
I don't think the new naming has a huge advantage (in fact I think
the old one actually is a little better, but the biggest argument here
really is to not change something if we don't have to).

That will massively reduce the churn at the cost of Kent having to
rework the code a bit, but that seems like a worthwhile tradeoff and
one that we've usuall made in the past.

      reply	other threads:[~2022-08-09  8:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220808024128.3219082-1-willy@infradead.org>
2022-08-08  2:41 ` [PATCH v5 27/32] PCI/P2PDMA: Convert to printbuf Matthew Wilcox (Oracle)
2022-08-08 17:51   ` Bjorn Helgaas
2022-08-08 18:42     ` Kent Overstreet
2022-08-09  2:07       ` Bjorn Helgaas
2022-08-09  8:00         ` Christoph Hellwig [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=YvIULAsLGMNVdPek@infradead.org \
    --to=hch@infradead.org \
    --cc=helgaas@kernel.org \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=pmladek@suse.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;
as well as URLs for NNTP newsgroup(s).