public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Enrico Demarin <enricod@videotron.ca>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Chuck Lever <cel@citi.umich.edu>, linux-kernel@vger.kernel.org
Subject: Re: Ibm Serveraid Problem with 2.4.25
Date: Mon, 01 Mar 2004 13:41:06 -0500	[thread overview]
Message-ID: <1078166466.4444.3.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0403011505150.5314-100000@dmt.cyclades>

Hi Marcelo,

Add mpt fusion driver to the list, it exhibits the problem as well.

- Enrico

On Mon, 2004-03-01 at 13:23, Marcelo Tosatti wrote:
> On Mon, 1 Mar 2004, Chuck Lever wrote:
> 
> > hi marcelo-
> > 
> > your "fix" will break readahead again for NFS.  with the ">=" as you
> > propose, the read ahead code will never be able to read the last page of
> > the file as a coalesced read, it will always be a separate 4KB read.
> > 
> > the problem is not the readahead code, it is the driver code that tries
> > to read beyond the end of the device.  my change merely exposed this
> > misbehavior.
> > 
> > so there is a broken assumption somewhere about how the index of the last
> > page of a file/device is computed.  i think it is a problem when the file
> > ends exactly on a page boundary.
> >
> > alain, if you don't use the NFS client, marcelo's fix should work just
> > fine for you.  but i believe that in general it is incorrect.
> 
> Okey, most drivers do no exhibit this problem indeed.
> 
> We should try to fix the problematic drivers, then.
> 
> If we can't do it easily and in a straightforward manner, I'm afraid we
> will have to undo your change because even if the "read end beyond of
> device" accesses are harmless (are they really harmless?), they must
> fixed.
> 
> Agreed?
> 
> I'll take a look at them later today, but I'm no expert, so help is very
> appreciated.
> 
> We know that these have problems:
> 
> - Promise ATA
> - ips (serveraid)
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  parent reply	other threads:[~2004-03-01 18:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-26  9:12 Ibm Serveraid Problem with 2.4.25 Jo Christian Buvarp
2004-02-26 23:48 ` Enrico Demarin
2004-02-27  1:48   ` Enrico Demarin
2004-02-27  3:14     ` Marcelo Tosatti
2004-02-27  2:37       ` Enrico Demarin
2004-02-27  7:16       ` Jo Christian Buvarp
2004-02-27 14:36         ` Marcelo Tosatti
2004-03-01  2:10           ` Alain Fauconnet
2004-03-01  3:10             ` Enrico Demarin
2004-03-01  3:30               ` Alain Fauconnet
2004-03-01 15:01                 ` Enrico Demarin
2004-03-01 15:51             ` Marcelo Tosatti
2004-03-01 17:24               ` Chuck Lever
2004-03-01 18:23                 ` Marcelo Tosatti
2004-03-01 18:39                   ` Chuck Lever
2004-03-01 18:41                   ` Enrico Demarin [this message]
2004-03-02  5:18                     ` Chuck Lever
     [not found] <Pine.LNX.4.44.0403011149560.4148-200000@dmt.cyclades>
2004-03-01 15:38 ` Jo Christian Buvarp
  -- strict thread matches above, loose matches on Subject: below --
2004-03-01 21:38 Alan Swanson

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=1078166466.4444.3.camel@localhost.localdomain \
    --to=enricod@videotron.ca \
    --cc=cel@citi.umich.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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