linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Daniel Gomez <da.gomez@samsung.com>,
	Ryan Roberts <ryan.roberts@arm.com>,
	Barry Song <v-songbaohua@oppo.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Luis Chamberlain <mcgrof@kernel.org>,
	Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: Swap Min Odrer
Date: Tue, 7 Jan 2025 11:31:05 +0100	[thread overview]
Message-ID: <ebe3dd53-eb4b-419f-93e9-914236161975@redhat.com> (raw)
In-Reply-To: <20250107094347.l37isnk3w2nmpx2i@AALNPWDAGOMEZ1.aal.scsc.local>

On 07.01.25 10:43, Daniel Gomez wrote:
> Hi,

Hi,

> 
> High-capacity SSDs require writes to be aligned with the drive's
> indirection unit (IU), which is typically >4 KiB, to avoid RMW. To
> support swap on these devices, we need to ensure that writes do not
> cross IU boundaries. So, I think this may require increasing the minimum
> allocation size for swap users.

How would we handle swapout/swapin when we have smaller pages (just 
imagine someone does a mmap(4KiB))?

Could this be something that gets abstracted/handled by the swap 
implementation? (i.e., multiple small folios get added to the swapcache 
but get written out / read in as a single unit?).

I recall that we have been talking about a better swap abstraction for 
years :)

Might be a good topic for LSF/MM (might or might not be a better place 
than the MM alignment session).

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2025-01-07 10:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250107094349eucas1p1c973738624046458bbd8ca980cf6fe33@eucas1p1.samsung.com>
2025-01-07  9:43 ` Daniel Gomez
2025-01-07 10:31   ` David Hildenbrand [this message]
2025-01-07 12:29     ` Daniel Gomez
2025-01-07 16:41       ` David Hildenbrand
2025-01-08 14:14         ` Daniel Gomez
2025-01-08 20:36           ` David Hildenbrand
2025-01-08 21:19             ` Chris Li
2025-01-08 21:24               ` David Hildenbrand
2025-01-16  8:38                 ` Chris Li
2025-01-20 12:02                   ` David Hildenbrand
2025-01-09  3:38               ` David Rientjes
2025-01-08 21:09         ` Chris Li
2025-01-08 21:05       ` Chris Li

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=ebe3dd53-eb4b-419f-93e9-914236161975@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=da.gomez@samsung.com \
    --cc=linux-mm@kvack.org \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.com \
    --cc=ryan.roberts@arm.com \
    --cc=v-songbaohua@oppo.com \
    /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