public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Richard Scobie <r.scobie@clear.net.nz>, xfs@oss.sgi.com
Subject: Re: file streams allocator behavior
Date: Sat, 25 Oct 2014 16:26:54 -0500	[thread overview]
Message-ID: <544C159E.8010408@hardwarefreak.com> (raw)
In-Reply-To: <544BF26F.6000708@clear.net.nz>

On 10/25/2014 01:56 PM, Richard Scobie wrote:
> Stan Hoeppner said:
> 
>> How can I disable or change the filestreams behavior so all files go
>> into the one AG for the single directory test?
> 
> Hi Stan,
> 
> Instead of mounting with -o filestreams, would using the chattr flag
> instead help?
> 
> See
> http://xfs.org/docs/xfsdocs-xml-dev/XFS_User_Guide/tmp/en-US/html/ch06s16.html

That won't help.  That turns it on (if it's not enabled by default these
days).  I need to turn off the behavior I'm seeing, whether it's due to
the filestreams allocator or default inode64.  Then again it may not be
possible to turn it off...

Anyone have other ideas on how to accomplish my goal?  Parallel writes
to a single AG on the outer platter edge vs the same to all AGs across
the entire platter?  I'm simply trying to demonstrate the differences in
aggregate bandwidth due to the extra seek latency of all AGs case.

Thanks,
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-10-25 21:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-25 18:56 file streams allocator behavior Richard Scobie
2014-10-25 21:26 ` Stan Hoeppner [this message]
2014-10-26 14:26   ` Brian Foster
2014-10-26 17:26     ` Stan Hoeppner
2014-10-26 22:18       ` Brian Foster
  -- strict thread matches above, loose matches on Subject: below --
2014-10-25 18:12 Stan Hoeppner
2014-10-26 23:56 ` Dave Chinner
2014-10-27 23:24   ` Stan Hoeppner

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=544C159E.8010408@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=r.scobie@clear.net.nz \
    --cc=xfs@oss.sgi.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