Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>,
	Nirmoy Das <nirmoy.das@intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Thomas Hellstr_m <thomas.hellstrom@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [RFC PATCH 0/2] Implement vma madvise ioctl
Date: Wed, 24 May 2023 22:12:44 +0200	[thread overview]
Message-ID: <673b857b-412d-152f-eede-e62fe9454060@linux.intel.com> (raw)
In-Reply-To: <ZG5Xx1R2xh/tf0f8@DUT025-TGLU.fm.intel.com>


On 5/24/2023 8:30 PM, Matthew Brost wrote:
> On Wed, May 24, 2023 at 02:36:46PM +0200, Nirmoy Das wrote:
>> Sending this initial RFC patch series for vma madvise ioctl
>> to gether feedback if this the correct way to do that.
>>
>> I am adding two expected options for userspace to pass
>>
>> DRM_XE_VMA_MADVISE_WILLNEED:
>> 	* Set ttm priority to normal/high(if cap permits)
>> 	* Make sure VMAs are in allowed placement and bound.
>>
>> DRM_XE_VMA_MADVISE_DONTNEED:
>> 	* Set ttm priority to low so the BO belong to the vma
>> 	become early target for eviction.
>> 	* Make sure VMAs are not bound.
>>
>> Questions:
>> Should this be part of DRM_IOCTL_XE_VM_MADVISE rather than creating new ioctl?
>>
> Def not a new IOCTL. Let's take a step back, what are you trying to
> implement that the current DRM_IOCTL_XE_VM_MADVISE IOCTL / VM bind IOCTL
> does not support?

AFAIU at this moment:

MADVISE_WILLNEED  ==  XE_VM_BIND_OP_PREFETCH + DRM_XE_VM_MADVISE_PRIORITY
MADVISE_DONTNEED  ==  XE_VM_BIND_OP_UNMAP + DRM_XE_VM_MADVISE_PRIORITY

So unless we need explicit madvise ioctl or vm_madvise ioctl options for UMD,
I think we can have madvise equivalent with above vm bind and vm madvise ioctl.

Hi Thomas, Joonas,

What do you think ?


Regards,

Nirmoy

>
> Matt
>
>> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>> Cc: Matthew Brost <matthew.brost@intel.com>
>>
>> Nirmoy Das (2):
>>    drm/xe: Expose vma bind-unbind functions
>>    drm/xe: Implement madvise ioctl for vma
>>
>>   drivers/gpu/drm/xe/Makefile         |   1 +
>>   drivers/gpu/drm/xe/xe_device.c      |   2 +
>>   drivers/gpu/drm/xe/xe_vm.c          |  52 +++----
>>   drivers/gpu/drm/xe/xe_vm.h          |   3 +
>>   drivers/gpu/drm/xe/xe_vma_madvise.c | 223 ++++++++++++++++++++++++++++
>>   drivers/gpu/drm/xe/xe_vma_madvise.h |  15 ++
>>   include/uapi/drm/xe_drm.h           |  28 ++++
>>   7 files changed, 296 insertions(+), 28 deletions(-)
>>   create mode 100644 drivers/gpu/drm/xe/xe_vma_madvise.c
>>   create mode 100644 drivers/gpu/drm/xe/xe_vma_madvise.h
>>
>> -- 
>> 2.39.0
>>

  reply	other threads:[~2023-05-24 20:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 12:36 [Intel-xe] [RFC PATCH 0/2] Implement vma madvise ioctl Nirmoy Das
2023-05-24 12:36 ` [Intel-xe] [RFC PATCH 1/2] drm/xe: Expose vma bind-unbind functions Nirmoy Das
2023-05-24 12:36 ` [Intel-xe] [RFC PATCH 2/2] drm/xe: Implement madvise ioctl for vma Nirmoy Das
2023-05-24 12:39 ` [Intel-xe] ✓ CI.Patch_applied: success for Implement vma madvise ioctl Patchwork
2023-05-24 12:41 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-24 12:45 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-05-24 18:30 ` [Intel-xe] [RFC PATCH 0/2] " Matthew Brost
2023-05-24 20:12   ` Nirmoy Das [this message]
2023-05-30 13:19     ` Thomas Hellström
2023-05-30 15:12       ` Thomas Hellström
2023-05-30 15:18       ` Nirmoy Das
2023-05-30 15:37         ` Thomas Hellström
2023-05-30 15:42           ` Nirmoy Das

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=673b857b-412d-152f-eede-e62fe9454060@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=matthew.brost@intel.com \
    --cc=nirmoy.das@intel.com \
    --cc=thomas.hellstrom@linux.intel.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