U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] drivers: block: Allow to cache 4K blocks by default
Date: Mon, 10 Dec 2018 07:28:11 -0500	[thread overview]
Message-ID: <20181210122811.GI8702@bill-the-cat> (raw)
In-Reply-To: <57c1b461-4663-2cf3-1415-af63bf2ed599@denx.de>

On Mon, Dec 10, 2018 at 05:13:58AM +0100, Marek Vasut wrote:
> On 12/09/2018 09:55 AM, Jan Kiszka wrote:
> > The default settings of the block cache so far only allow to hold single
> > 1K blocks. However, larger filesystems tend to use 4K. Failing to cache
> > those massively degrades access performance unless you manually tune the
> > cache first. This is not desirable.
> > 
> > Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> 
> I submitted the same patch before [1], oddly enough it was not picked by
> Tom.
> 
> [1]
> http://u-boot.10912.n7.nabble.com/PATCH-RFC-blk-Increase-cache-element-size-td337975.html

Based on a quick re-read, I had filed that patch as "Marek says he'll
look into a more complex but general scheme".  If that's not the case
then yes, we can just do that.  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181210/e6a3af73/attachment.sig>

  parent reply	other threads:[~2018-12-10 12:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-09  8:55 [U-Boot] [PATCH] drivers: block: Allow to cache 4K blocks by default Jan Kiszka
2018-12-10  4:13 ` Marek Vasut
2018-12-10  6:18   ` Jan Kiszka
2018-12-10 12:28   ` Tom Rini [this message]
2018-12-20  8:45     ` Marek Vasut
2019-01-03 15:42       ` Jan Kiszka
2019-01-03 15:52         ` Tom Rini

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=20181210122811.GI8702@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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