From: Andrea Arcangeli <andrea@suse.de>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Benjamin LaHaise <bcrl@redhat.com>,
linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: [PATCH] PAGE_SIZE IO for RAW (RAW VARY)
Date: Thu, 10 Jan 2002 11:34:22 +0100 [thread overview]
Message-ID: <20020110113421.H3357@inspiron.school.suse.de> (raw)
In-Reply-To: <E16ORfZ-0002Zu-00@the-village.bc.nu> <200201092348.g09NmHg25671@eng2.beaverton.ibm.com>
In-Reply-To: <200201092348.g09NmHg25671@eng2.beaverton.ibm.com>; from pbadari@us.ibm.com on Wed, Jan 09, 2002 at 03:48:17PM -0800
On Wed, Jan 09, 2002 at 03:48:17PM -0800, Badari Pulavarty wrote:
> Alan,
>
> >
> > > If it is not reasonable to fix all the brokern drivers,
> > > how about making this configurable (to do variable size IO) ?
> > > Do you favour this solution ?
> >
> > We have hardware that requires aligned power of two for writes (ie 4K on
> > 4K boundaries only). The 3ware is one example Jeff Merkey found
> >
>
> emm.. come to think of it, I can easily (2 line) change my patch to
> do 512 byte buffer heads till we get PAGE alignment and then start
> issuing 4K IO buffer heads. What do you think ? will this work ?
you should make sure the buffer is naturally aligned with the b_size (so
you emulate the change of blocksize in a filesystem), if it wasn't the
case you should fix it.
>
> And also, do you know any low level drivers Ben mentioning:
>
> > low level drivers, some of which assume that
> > all buffer heads within a request have the same block size.
>
> Is it still true for 2.4 ?
yes, you simply need to call submit_bh or to use separate ll_rw_blocks
when you change b_size.
>
> Regards,
> Badari
Andrea
next prev parent reply other threads:[~2002-01-10 10:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 17:41 Badari Pulavarty
2002-01-09 17:58 ` Benjamin LaHaise
2002-01-09 18:12 ` Badari Pulavarty
2002-01-09 18:21 ` Benjamin LaHaise
2002-01-09 19:28 ` Badari Pulavarty
2002-01-09 19:49 ` Benjamin LaHaise
2002-01-09 22:58 ` Alan Cox
2002-01-09 23:48 ` Badari Pulavarty
2002-01-10 10:34 ` Andrea Arcangeli [this message]
2002-01-10 10:29 ` Andrea Arcangeli
2002-01-10 10:18 ` Andrea Arcangeli
2002-01-10 10:22 ` Jens Axboe
2002-01-10 10:47 ` Andrea Arcangeli
2002-01-10 10:51 ` Jens Axboe
2002-01-10 11:09 ` Andrea Arcangeli
2002-01-10 16:58 ` Badari Pulavarty
2002-01-11 13:52 ` Andrea Arcangeli
2002-01-10 19:24 ` Badari Pulavarty
2002-01-10 20:00 ` Alan Cox
2002-01-10 21:03 ` Badari Pulavarty
2002-01-10 21:26 ` Alan Cox
2002-01-10 21:15 ` Badari Pulavarty
2002-01-15 3:16 ` Joel Becker
2002-01-10 7:12 ` Jens Axboe
2002-01-09 18:13 ` Jens Axboe
2002-01-09 22:56 ` Alan Cox
2002-01-09 23:20 ` Badari Pulavarty
2002-01-10 0:23 ` Alan Cox
2002-01-10 4:06 ` GOTO Masanori
[not found] <200201091741.g09HfAI17240@eng2.beaverton.ibm.com.suse.lists.linux.kernel>
[not found] ` <20020109125845.B12609@redhat.com.suse.lists.linux.kernel>
2002-01-09 18:15 ` Andi Kleen
[not found] <200201102153.g0ALrl402482@eng2.beaverton.ibm.com>
2002-01-10 22:11 ` Alan Cox
2002-01-10 22:20 ` Badari Pulavarty
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=20020110113421.H3357@inspiron.school.suse.de \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=pbadari@us.ibm.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
all inboxes | Powered by JetHome®