From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: USB file mmap
Date: Mon, 7 Jul 2014 09:34:30 -0700 [thread overview]
Message-ID: <20140707163430.GA1137@kroah.com> (raw)
In-Reply-To: <CAC-LjFsS2S0h4+X0eng+MiZ7O-2cmB9fgU1_+sAVr5hRobjRFA@mail.gmail.com>
On Mon, Jul 07, 2014 at 07:30:07PM +0530, Jeshwanth Kumar N K wrote:
> Hello List,
> I am trying to understand mmap on files residing in USB flash, so can you
> please give a pointer from where I can start to understand this? I mean how it
> works, and which part in kernel takes care of it.
That's a _huge_ stack you are talking about here involving a vfs, the
memory management core, a filesystem, block layer, SCSI, and USB, at the
very least.
What _exactly_ are you looking to understand here? And where in the
code have you looked and need help with? What documents have you read
that were unclear? And why do you need this information?
greg k-h
next prev parent reply other threads:[~2014-07-07 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 14:00 USB file mmap Jeshwanth Kumar N K
2014-07-07 16:34 ` Greg KH [this message]
2014-07-07 19:56 ` Jeshwanth Kumar N K
2014-07-07 20:29 ` Greg Kroah-Hartman
2014-07-07 20:32 ` Greg Kroah-Hartman
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=20140707163430.GA1137@kroah.com \
--to=greg@kroah.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).