linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bharat Kumar Gogada <bharatku@xilinx.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "jglisse@redhat.com" <jglisse@redhat.com>
Subject: HMM hmm_range parameter usage
Date: Mon, 6 Jun 2022 12:27:20 +0000	[thread overview]
Message-ID: <BY5PR02MB69474464D28B2E205FE47146A5A29@BY5PR02MB6947.namprd02.prod.outlook.com> (raw)

Hi All,

In 5.4 kernel hmm_range structure has pfn_shift parameter. 
This parameter is removed in the latest kernel.

Can any one help me understand usage of this parameter ?

In 5.4 kernel, if this parameter set to PAGE_SHIFT, does it mean HMM framework 
expects user buffers to be 4K aligned, i.e which are allocated via mmap/aligned_alloc ?

Does HMM have any alignment requirements in 5.4 or current kernel ? Will it work 
with buffers allocated via malloc ?

Regards,
bharat 

 


             reply	other threads:[~2022-06-06 12:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 12:27 Bharat Kumar Gogada [this message]
2022-06-06 13:56 ` Alistair Popple

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=BY5PR02MB69474464D28B2E205FE47146A5A29@BY5PR02MB6947.namprd02.prod.outlook.com \
    --to=bharatku@xilinx.com \
    --cc=jglisse@redhat.com \
    --cc=linux-mm@kvack.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