kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: ksashtekar@gmail.com (Kaustubh Ashtekar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: mmap on a block device
Date: Tue, 7 Jun 2011 12:14:11 +0530	[thread overview]
Message-ID: <BANLkTi=d5P+emUdBFCcB+8iwiPjsrc9tjQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinf3mj-jHn6abOw5Kc7j+b2L+9otA@mail.gmail.com>

Done. mmap was successful.

Is it a good idea to mmap a block device. A block device being much bigger
than the available virtual address space, I will have to map it multiple
times while working on various parts of the block device.

BR,
Kaustubh

On Tue, Jun 7, 2011 at 11:47 AM, Rajat Sharma <fs.rajat@gmail.com> wrote:

> yes its fairly possible, go ahead and try it.
>
> On Tue, Jun 7, 2011 at 9:57 AM, Kaustubh Ashtekar <ksashtekar@gmail.com>
> wrote:
> > Hello All,
> > Is it possible to mmap on a block device? I am writing my own kernel
> space
> > filesystem on Linux (academic project). I am writing a user space tool to
> > format the block device (again my own ramdisk driver). It would be much
> > simpler if I could just mmap the block device into my address space.
> > -Kaustubh
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110607/0567cf86/attachment.html 

  reply	other threads:[~2011-06-07  6:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07  4:27 mmap on a block device Kaustubh Ashtekar
2011-06-07  6:17 ` Rajat Sharma
2011-06-07  6:44   ` Kaustubh Ashtekar [this message]
2011-06-07 14:53     ` Dave Hylands

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='BANLkTi=d5P+emUdBFCcB+8iwiPjsrc9tjQ@mail.gmail.com' \
    --to=ksashtekar@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).