Re: [PATCH v2 1/8] lib/printbuf: New data structure for heap-allocated strings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Kent Overstreet <kent.overstreet@xxxxxxxxx>
Subject: Re: [PATCH v2 1/8] lib/printbuf: New data structure for heap-allocated strings
From: Christoph Hellwig <hch@xxxxxx>
Date: Fri, 22 Apr 2022 06:20:17 +0200
Cc: linux-kernel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, hch@xxxxxx, hannes@xxxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, linux-clk@xxxxxxxxxxxxxxx, linux-tegra@xxxxxxxxxxxxxxx, linux-input@xxxxxxxxxxxxxxx, roman.gushchin@xxxxxxxxx, rostedt@xxxxxxxxxxx
In-reply-to: <20220421234837.3629927-7-kent.overstreet@gmail.com>
References: <20220421234837.3629927-1-kent.overstreet@gmail.com> <20220421234837.3629927-7-kent.overstreet@gmail.com>
User-agent: Mutt/1.5.17 (2007-11-01)

I still see absolutel no reason to bloat the kernel with a duplicate
of the existing seq_buf functionality.  Please use that and improve it
where needed for your use case.

Follow-Ups:
- Re: [PATCH v2 1/8] lib/printbuf: New data structure for heap-allocated strings
  - From: Kent Overstreet

References:
- [PATCH 0/4] Printbufs & shrinker OOM reporting
  - From: Kent Overstreet
- [PATCH v2 1/8] lib/printbuf: New data structure for heap-allocated strings
  - From: Kent Overstreet

Prev by Date: Re: [PATCH v4 bpf 0/4] vmalloc: bpf: introduce VM_ALLOW_HUGE_VMAP
Next by Date: Re: make the blkcg and blkcg structures private
Previous by thread: [PATCH v2 1/8] lib/printbuf: New data structure for heap-allocated strings
Next by thread: Re: [PATCH v2 1/8] lib/printbuf: New data structure for heap-allocated strings
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux