From: Jens Axboe <axboe@suse.de>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
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:51:51 +0100 [thread overview]
Message-ID: <20020110115151.T19814@suse.de> (raw)
In-Reply-To: <20020109132148.C12609@redhat.com> <200201091928.g09JSdH23535@eng2.beaverton.ibm.com> <20020110111825.C3357@inspiron.school.suse.de> <20020110112225.S19814@suse.de> <20020110114704.I3357@inspiron.school.suse.de>
In-Reply-To: <20020110114704.I3357@inspiron.school.suse.de>
On Thu, Jan 10 2002, Andrea Arcangeli wrote:
> On Thu, Jan 10, 2002 at 11:22:25AM +0100, Jens Axboe wrote:
> > On Thu, Jan 10 2002, Andrea Arcangeli wrote:
> > > On Wed, Jan 09, 2002 at 11:28:39AM -0800, Badari Pulavarty wrote:
> > > > Ben,
> > > >
> > > > By any chance do you have a list of drivers that assume this ?
> > > > What does it take to fix them ?
> > > >
> > > > I think Jens BIO changes for 2.5 will fix this problem. But 2.4
> > > > needs a solution in this area too. This patch showed significant
> > > > improvement for database workloads.
> > >
> > > I didn't checked the implementation but as far as the blkdev is
> > > concerned the b_size changes without notification as soon as you
> > > 'mkfs -b somethingelse' and then mount the fs. So it cannot break
> > > as far I can tell. The only important thing is that b_size stays
> > > between 512 and 4k.
> >
> > The concern is/was differently sized buffer_heads in the same
> > request, ie b_size changing as you iterate through the chunks of one
> > request.
>
> ok, I don't expect problems there. It can happen for example if you
> create a snapshot with 4k and then you switch back the original volume
> to 1k. the physical volume will get mixed b_size colaesced into the
> same request.
Well I don't expect problems either, however Jeff Merkey did report them
but see my previous mail on that (validity of that report is
questionable).
I still wouldn't feel to good doing this, and just because snapshotting
opens the possibility for this to happen doesn't mean it a) ever
triggered in real life, and b) works on all devices.
--
Jens Axboe
next prev parent reply other threads:[~2002-01-10 10:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 17:41 [PATCH] PAGE_SIZE IO for RAW (RAW VARY) 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
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 [this message]
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=20020110115151.T19814@suse.de \
--to=axboe@suse.de \
--cc=andrea@suse.de \
--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