From: Christophe Varoqui <christophe.varoqui@free.fr>
To: Peter Koutoupis <Peter_Koutoupis@us.xyratex.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: RE: directio / readsector0
Date: Tue, 03 Jul 2007 23:08:14 +0200 [thread overview]
Message-ID: <1183496894.8402.18.camel@localhost.localdomain> (raw)
In-Reply-To: <9F94CC89AA0F524CBA8A619D43C4AED80B0731@XYUS-EX22.xyus.xyratex.com>
Le lundi 02 juillet 2007 à 16:39 -0700, Peter Koutoupis a écrit :
> Christophe,
>
> My only concern is that we have an application that works on top of
> device-mapper and multipath-tools; and in the multipath.conf file
> under friendly user names we specify the readsector0 due to certain
> limitations with our recent line of RAID products. That means many
> customers hold those settings. If it is preferred to remove the
> readsector0 completely, we can possibly send patches to customers to
> have that parameter altered. Although, please excuse my ignorance but
> what is to stop from implementing directio, still leaving the
> readsector0 intact?
>
What really matters is your testing for regressions with the directio
checker.
readsector0 phasing out could be made smooth, by making the
configuration term point to the directio checker.
The incentive there is to not have redundant (and thus confusing)
checkers to maintain.
Regards,
cvaroqui
next prev parent reply other threads:[~2007-07-03 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 21:29 directio / readsector0 Christophe Varoqui
[not found] ` <9F94CC89AA0F524CBA8A619D43C4AED80B0731@XYUS-EX22.xyus.xyratex.com>
2007-07-03 21:08 ` Christophe Varoqui [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-19 20:08 Christophe Varoqui
2007-06-19 20:06 ` Peter Koutoupis
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=1183496894.8402.18.camel@localhost.localdomain \
--to=christophe.varoqui@free.fr \
--cc=Peter_Koutoupis@us.xyratex.com \
--cc=dm-devel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.