From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH v2 3/3] disk: read into cache directly
Date: Wed, 2 Mar 2016 06:46:14 +0300 [thread overview]
Message-ID: <56D66206.8040201@gmail.com> (raw)
In-Reply-To: <CAEaD8JN3CU8cmQhVMOpPiGhr9caeoGAJ6PRzAf20yt-r5f_N=Q@mail.gmail.com>
02.03.2016 03:22, Vladimir 'phcoder' Serbinenko пишет:
> Is there any way this patch reclaims unused memory in case of partial cache
> eviction?
Not yet, I wanted to make sure base looks sane first. Are there any
cases of partial eviction besides blocklist write?
> If not it could potentially water lots of memory. One thing you
> need to consider is that initrd for Solaris can easily be 60% of total RAM
> (300 MiB on 512MiB machine) What if requested read is bigger than risk
> cache size?
>
Not sure I parse it; but yes, it puts more stress on cache by requiring
unfragmented memory. If we follow this route we need to gracefully fall
back to cache element size.
Do we have any reasonable chance to separate aligned and non-aligned
memory pools?
next prev parent reply other threads:[~2016-03-02 3:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 0:14 [PATCH v2 0/3] some disk reworking reposted Leif Lindholm
2016-03-02 0:14 ` [PATCH v2 1/3] disk: Add support for device-specific malloc function Leif Lindholm
2016-03-02 0:14 ` [PATCH v2 2/3] efidisk: implement alignment-respecting " Leif Lindholm
2016-03-02 3:46 ` Andrei Borzenkov
2016-03-02 14:00 ` Leif Lindholm
2016-03-02 0:14 ` [PATCH v2 3/3] disk: read into cache directly Leif Lindholm
2016-03-02 0:22 ` Vladimir 'phcoder' Serbinenko
2016-03-02 3:46 ` Andrei Borzenkov [this message]
2016-03-02 9:55 ` Vladimir 'phcoder' Serbinenko
2016-03-03 0:04 ` Elliott, Robert (Persistent Memory)
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=56D66206.8040201@gmail.com \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.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).