public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@gmail.com>
To: Bob Copeland <email@bobcopeland.com>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>,
	Roushan Ali <roushan.ali@gmail.com>,
	Nathan Scott <nathans@sgi.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: file system block size
Date: Tue, 18 Oct 2005 08:30:24 -0700	[thread overview]
Message-ID: <1129649424.23632.55.camel@localhost.localdomain> (raw)
In-Reply-To: <b6c5339f0510180812p3ff6d0b1ia204b28c4e50186d@mail.gmail.com>

On Tue, 2005-10-18 at 11:12 -0400, Bob Copeland wrote:
> > Indeed, it makes everything harder.  Have a look at ntfs in the kernel
> > which has to cope with file system block sizes between 512 bytes and
> > several hundred kiB (at least they are in powers of two thank
> > goodness...).  You end up not being able to use a lot of generic
> > functions as you for example need to lock multiple pages which needs to
> > be ordered correctly, etc...  If you look at the latest -mm kernel, the
> > ntfs driver there has file write(2) support for any cluster size and you
> > will see an example of the multiple page locking problem solution there.
> 
> Any chance this will make it into common code?  I also need it for my
> filesystem driver (here: http://bobcopeland.com/karma/).  So far I've
> only done read side which is not too bad, but as you say writing makes
> things complicated.
> 
> That, and the extent-supporting mpage_readpages would make me a happy person.

Can you elaborate ? What would you like to see in mpage_readpages() ?
Christoph recently posted patches to add support for getblocks() in
mpage_readpages().  What else do you need ?


Thanks,
Badari


  reply	other threads:[~2005-10-18 15:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18  5:52 file system block size Roushan Ali
2005-10-18 14:12 ` Nathan Scott
2005-10-18 14:36   ` Anton Altaparmakov
2005-10-18 15:12     ` Bob Copeland
2005-10-18 15:30       ` Badari Pulavarty [this message]
2005-10-18 15:42         ` Bob Copeland

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=1129649424.23632.55.camel@localhost.localdomain \
    --to=pbadari@gmail.com \
    --cc=aia21@cam.ac.uk \
    --cc=email@bobcopeland.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@sgi.com \
    --cc=roushan.ali@gmail.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