public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Łukasz Fibinger" <lucke@o2.pl>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: RESVSP problems
Date: Mon, 7 May 2007 20:58:32 +0200	[thread overview]
Message-ID: <200705072058.32679.lucke@o2.pl> (raw)
In-Reply-To: <463F7368.8090101@sandeen.net>

On Monday 07 of May 2007, you wrote:
> You've probably hit:
> http://oss.sgi.com/bugzilla/show_bug.cgi?id=418
> unwritten extents remain unwritten after mmap() modifies them
>
> Bug dchinner about it... ;-)

Dave, consider it a bugging from my humble self :-)

> yeah... ISTR that the arguments are funky.  I can't remember if it's a
> bug or not.  :)  FWIW, allocsp just writes zeros to the file, so you
> could do it just as well from userspace w/ no fancy ioctls...  ALLOCSP
> is a bit pointless if you ask me... though maybe someone knows why it's
> there :)

Let me say that I have noticed that using ALLOCSP seems to create less extents 
than posix_fallocate/manual zeroing.

Thanks for your answer. Incidentally, I'm really happy that XFS has been 
bestowed upon linux users. Thanks for all your work, guys :-)

Cheers,

Luke

  reply	other threads:[~2007-05-07 18:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 18:04 RESVSP problems Łukasz Fibinger
2007-05-07 18:43 ` Eric Sandeen
2007-05-07 18:58   ` Łukasz Fibinger [this message]
2007-05-08  0:59     ` David Chinner
2007-05-08  5:03       ` Eric Sandeen
2007-05-08  5:25         ` David Chinner
  -- strict thread matches above, loose matches on Subject: below --
2007-05-24 11:24 Łukasz Fibinger
2007-05-25  5:06 ` David Chinner
2007-05-25 10:24   ` Łukasz Fibinger
2007-05-25 11:24     ` David Chinner
2007-05-25 13:37       ` Łukasz Fibinger
2007-05-25 14:19       ` Christoph Hellwig
2007-05-28  0:50         ` David Chinner

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=200705072058.32679.lucke@o2.pl \
    --to=lucke@o2.pl \
    --cc=sandeen@sandeen.net \
    --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