public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Cc: jeremy@classic.engr.sgi.com
Subject: o_direct-11 and blkdev-pagecache-8
Date: Thu, 2 Aug 2001 15:05:29 +0200	[thread overview]
Message-ID: <20010802150529.A24436@athlon.random> (raw)

Here the latest release against 2.4.8pre3.

For the blkdev-pagecache I decreased performance going to 1k I/O
granularity to provide total backwards compatibility, otherwise it was
not possible to read the last bytes of the device if the size of the
device was not a multiple of 4k and there's no way to work around that
without intensive changes :(, this in turn means the doing O_DIRECT on
the blkdevice now has a constraint of 1k I/O granularity on the
read/write API (not anymore the more restrictive 4k granularity).

The O_DIRECT patch includes a one liner I got from the GFS folks to
update the i_size of the inode correctly.

They must be applyed in order:

	ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/patches/v2.4/2.4.8pre3/o_direct-11
	ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/patches/v2.4/2.4.8pre3/blkdev-pagecache-8

Now it would be nice to have a patch incremental to those so that rawio
also uses the preallocated per-file iobuf (note: the preallocation
should happen in the rawio layer, not in the vfs like we just do with
the generic O_DIRECT).

Andrea

             reply	other threads:[~2001-08-02 13:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02 13:05 Andrea Arcangeli [this message]
2001-08-05 16:28 ` blkdev-pagecache-11 Andrea Arcangeli
2001-08-05 16:29   ` blkdev-pagecache-11 Andrea Arcangeli

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=20010802150529.A24436@athlon.random \
    --to=andrea@suse.de \
    --cc=jeremy@classic.engr.sgi.com \
    --cc=linux-kernel@vger.kernel.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