From b3693de21ba31d3373264818921379633deef1b0 Mon Sep 17 00:00:00 2001 From: Bahadir Balban Date: Wed, 22 Oct 2008 21:15:53 +0300 Subject: [PATCH] Removed unnecessary comments --- tasks/mm0/include/vm_area.h | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/tasks/mm0/include/vm_area.h b/tasks/mm0/include/vm_area.h index ef28da1..57ed1aa 100644 --- a/tasks/mm0/include/vm_area.h +++ b/tasks/mm0/include/vm_area.h @@ -104,17 +104,6 @@ struct vm_pager { struct vm_pager_ops ops; /* The ops the pager does on area */ }; - -/* TODO: - * How to distinguish different devices handling page faults ??? - * A possible answer: - * - * If they are not mmap'ed, this is handled by the vfs calling that file's - * specific operations (e.g. even calling the device process). If they're - * mmap'ed, they adhere to a standard mmap_device structure kept in - * vm_file->priv_data. This is used by the device pager to map those pages. - */ - /* * Describes the in-memory representation of a resource. This could * point at a file or another resource, e.g. a device area, swapper space,