lkml.org 
[lkml]   [2007]   [Mar]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC] Heads up on sys_fallocate()
    On Fri, 02 Mar 2007 08:13:00 -0800 Badari Pulavarty <pbadari@us.ibm.com> wrote:

    > >
    > > > What about
    > > > if the
    > > > blocks already exists ? What would be return values in those cases ?
    > >
    > > 0 on success, other normal errors oetherwise..
    > >
    > > If asked for a range that includes already-allocated blocks, you just
    > > allocate any non-allocated blocks in the range, I think.
    >
    > Yes. What I was trying to figure out is, if there is a requirement that
    > interface need to return exact number of bytes it *really* allocated
    > (like write() or read()). I can't think of any, but just wanted to
    > through it out..

    Hopefully not, because posix didn't anticipate that.

    We could of course return a positive number on success, but it'd get
    tricky on 32-bit machines.

    > BTW, what is the interface for finding out what is the size of the
    > pre-allocated file ?

    stat.st_blocks?
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-03-02 18:09    [W:4.269 / U:0.504 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site