All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Higdon <jeremy@sgi.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: mpm@waste.org, SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC] Make the SCSI mempool allocations variable
Date: Wed, 10 Mar 2004 22:38:05 -0800	[thread overview]
Message-ID: <20040311063805.GM618504@sgi.com> (raw)
In-Reply-To: <1078932577.10834.44.camel@mulgrave>

On Wed, Mar 10, 2004 at 10:29:36AM -0500, James Bottomley wrote:
> 
> The best course of action is probably to put the patch in (since it has
> its current default at 128, it will change nothing) so that people who
> wish to play with increasing the allocation can.
> 
> To address the question of how you set this, I'd like more information
> about which filesystems and workloads find this useful, perhaps with a
> view to tying it to an indirect config option (CONFIG_ENTERPRISE or
> something).
> 
> James

Most of our users that would benefit from this would fall into the
"HPC" segment.  HPC meaning High Performance Computing.  That's
probably not very descriptive.  There is typically a lot of floating
point and large data sets.

There may be a database involved, but it's not traditional commercial
transaction processing, which typically has very small I/O requests.

Other users would be Broadcast, where they stream A/V streams to/from
a RAID device.

There are also sites that store large amounts of data keeping track
of things (people/places/etc.), looking for things, etc.

Maybe CONFIG_HPC or CONFIG_HIGH_BANDWIDTH_IO.  The longer and
clumsier the name, the more descriptive.  :-)

Filesystems?  Is there anything other than XFS?  :-)  :-)

jeremy

      reply	other threads:[~2004-03-11  6:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09 19:02 [RFC] Make the SCSI mempool allocations variable James Bottomley
2004-03-10  6:21 ` Jeremy Higdon
2004-03-10 10:07 ` Jeremy Higdon
2004-03-10 15:29   ` James Bottomley
2004-03-11  6:38     ` Jeremy Higdon [this message]

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=20040311063805.GM618504@sgi.com \
    --to=jeremy@sgi.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mpm@waste.org \
    /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.