public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Nelson Zhang <nxz@cypress.com>
Cc: "'David Cross'" <david.cross@cypress.com>,
	hirofumi@mail.parknet.co.jp, linux-kernel@vger.kernel.org
Subject: Re: EXPORT_SYMBOL(fat_get_block)
Date: Tue, 17 Aug 2010 07:54:03 -0700	[thread overview]
Message-ID: <20100817145403.GA28926@suse.de> (raw)
In-Reply-To: <ABE41F255A574632903665A7D1F90907@mis.cypress.com>

On Mon, Aug 16, 2010 at 06:57:54AM +0800, Nelson Zhang wrote:
> Hi David, Greg,
> 
> What I have done so far is following:
> 
> 1. Open a file 
> 2. Seek to the end of file

That just created a "sparse file"

> What I have not done is:
> 
> 3. mmap the whole file. 
> 
> Without #3, the file is not allocated until I write to the file.

That is by design.

> I think we can try to use mmap to allocate the file but we still need
> a function that can get file block info once the file is allocated.

No, why would you want the file block info?

Just treat it as a file, using mmap() and all the other userspace
goodness that we have to get data to a file very quickly.  You don't
need to preallocate the file from userspace, or anything else like that.

I suggest looking at some documentation on how to use the Unix file apis
properly to implement this better.

thanks,

greg k-h

  reply	other threads:[~2010-08-17 15:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 17:45 EXPORT_SYMBOL(fat_get_block) David Cross
2010-08-13 17:54 ` EXPORT_SYMBOL(fat_get_block) Greg KH
2010-08-13 18:43   ` EXPORT_SYMBOL(fat_get_block) David Cross
2010-08-13 18:50     ` EXPORT_SYMBOL(fat_get_block) Christoph Hellwig
2010-08-13 19:06       ` EXPORT_SYMBOL(fat_get_block) David Cross
2010-08-13 19:01     ` EXPORT_SYMBOL(fat_get_block) Greg KH
2010-08-13 19:17       ` EXPORT_SYMBOL(fat_get_block) David Cross
2010-08-13 19:28         ` EXPORT_SYMBOL(fat_get_block) Greg KH
2010-08-13 20:32           ` EXPORT_SYMBOL(fat_get_block) David Cross
2010-08-13 22:17             ` EXPORT_SYMBOL(fat_get_block) Greg KH
2010-08-13 23:22               ` EXPORT_SYMBOL(fat_get_block) David Cross
2010-08-14  0:25                 ` EXPORT_SYMBOL(fat_get_block) Greg KH
2010-08-14  1:12                   ` EXPORT_SYMBOL(fat_get_block) David Cross
2010-08-14  3:04                     ` EXPORT_SYMBOL(fat_get_block) Greg KH
2010-08-15 22:57                       ` EXPORT_SYMBOL(fat_get_block) Nelson Zhang
2010-08-17 14:54                         ` Greg KH [this message]
2010-08-17 15:40                           ` EXPORT_SYMBOL(fat_get_block) Christoph Hellwig
2010-08-17 15:54                             ` EXPORT_SYMBOL(fat_get_block) Greg KH
2010-08-13 17:54 ` EXPORT_SYMBOL(fat_get_block) Greg KH

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=20100817145403.GA28926@suse.de \
    --to=gregkh@suse.de \
    --cc=david.cross@cypress.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nxz@cypress.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