public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: GrandMasterLee <masterlee@digitalroadkill.net>
To: Michael Clark <michael@metaparadigm.com>
Cc: J Sloan <joe@tmsusa.com>, Simon Roscic <simon.roscic@chello.at>,
	Arjan van de Ven <arjanv@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Kernel 2.5] Qlogic 2x00 driver
Date: 16 Oct 2002 01:48:53 -0500	[thread overview]
Message-ID: <1034750930.2045.35.camel@localhost> (raw)
In-Reply-To: <3DAD09E3.2050602@metaparadigm.com>

On Wed, 2002-10-16 at 01:40, Michael Clark wrote:
...
> > Should I remove LVM all together, or just not use it? In your opinion.
> 
> I just didn't load the module after migrating my volumes. If the problem
> is a stack problem, then its probably not necessarily a bug in LVM
> - just the combination of it, ext3 and the qlogic driver don't mix well
> - so if its not being used, then it won't be increasing the stack footprint.
> 
> ~mc
> 

Not to be dense, but it's compiled into my kernel, that's why I ask. We
try not to use modules where we can help it. So I'm thinking, if no VG
are actively used, then LVM won't affect the stack much. I just don't
know if that's true or not. 

 --The GrandMaster

  reply	other threads:[~2002-10-16  6:42 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 19:20 [Kernel 2.5] Qlogic 2x00 driver Simon Roscic
2002-10-15 19:31 ` Arjan van de Ven
2002-10-15 19:53   ` Simon Roscic
2002-10-16  2:51     ` Michael Clark
2002-10-16  3:56       ` GrandMasterLee
2002-10-16  4:30         ` Michael Clark
2002-10-16  4:35           ` J Sloan
2002-10-16  4:43             ` GrandMasterLee
2002-10-16  6:03               ` Michael Clark
2002-10-16  6:31                 ` GrandMasterLee
2002-10-16  6:40                   ` Michael Clark
2002-10-16  6:48                     ` GrandMasterLee [this message]
2002-10-16  6:59                       ` Michael Clark
2002-10-16  4:58             ` GrandMasterLee
2002-10-16  5:28             ` Michael Clark
2002-10-16  5:40               ` Andreas Dilger
2002-10-17  1:59                 ` Andrew Vasquez
2002-10-17  2:44                   ` GrandMasterLee
2002-10-17  3:11                     ` Andrew Vasquez
2002-10-17  3:42                       ` GrandMasterLee
2002-10-17  9:40                       ` Michael Clark
2002-10-18  6:45                         ` GrandMasterLee
2002-10-16 16:28       ` Simon Roscic
2002-10-16 16:49         ` Michael Clark
2002-10-17  3:12           ` GrandMasterLee
2002-10-17  3:54             ` Michael Clark
2002-10-17  4:08               ` GrandMasterLee
2002-10-17  5:03                 ` Michael Clark
2002-10-16  5:02 ` GrandMasterLee
2002-10-16 16:38   ` Simon Roscic
2002-10-17  3:08     ` GrandMasterLee
2002-10-17 17:47       ` Simon Roscic
2002-10-18  6:42         ` GrandMasterLee
2002-10-18 15:11           ` Simon Roscic
  -- strict thread matches above, loose matches on Subject: below --
2002-10-19  2:17 rwhron

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=1034750930.2045.35.camel@localhost \
    --to=masterlee@digitalroadkill.net \
    --cc=arjanv@redhat.com \
    --cc=joe@tmsusa.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@metaparadigm.com \
    --cc=simon.roscic@chello.at \
    /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