From: Jon Bendtsen <jon+lvm@silicide.dk>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems and questions with LVM on a large raid system.
Date: Thu Mar 13 02:45:02 2003 [thread overview]
Message-ID: <3E7044D0.A7B8BBA6@silicide.dk> (raw)
In-Reply-To: 08628CA53C6CBA4ABAFB9E808A5214CB0142B3B7@mercury.infiniconsys.com
"Barry, Christopher" wrote:
>
> Wouldn't some of the processing be off-loaded to a dedicated controller?
\x7f
Yes, but would that matter (much) ?
JonB
next prev parent reply other threads:[~2003-03-13 2:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 21:03 [linux-lvm] Problems and questions with LVM on a large raid system Barry, Christopher
2003-03-13 2:45 ` Jon Bendtsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 13:53 Petro
2003-03-12 16:14 ` jon+lvm
2003-03-12 16:24 ` Kevin P. Fleming
2003-03-12 16:50 ` jon+lvm
2003-03-12 17:00 ` Kevin P. Fleming
2003-03-12 17:17 ` jon+lvm
2003-03-12 17:25 ` Kevin P. Fleming
2003-03-12 17:46 ` Petro
2003-03-13 2:44 ` Jon Bendtsen
2003-03-13 18:25 ` Petro
2003-03-14 2:32 ` Adrian Phillips
2003-03-15 13:50 ` Steven Lembark
2003-03-15 16:37 ` jon+lvm
2003-03-18 3:14 ` Heinz J . Mauelshagen
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=3E7044D0.A7B8BBA6@silicide.dk \
--to=jon+lvm@silicide.dk \
--cc=linux-lvm@sistina.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