[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110901164554.GB7641@infradead.org>
Date: Thu, 1 Sep 2011 12:45:54 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Jeremy Allison <jra@...ba.org>
Cc: Christoph Hellwig <hch@...radead.org>,
Ulrich Drepper <drepper@...adia.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Daniel Ehrenberg <dehrenberg@...gle.com>,
Jens Axboe <axboe@...nel.dk>, Jeff Moyer <jmoyer@...hat.com>,
linux-kernel@...r.kernel.org, linux-aio@...ck.org
Subject: Re: Approaches to making io_submit not block
On Thu, Sep 01, 2011 at 09:34:52AM -0700, Jeremy Allison wrote:
> >
> > (to match the naming of something like O_CLOEXEC) and be available to set
> > with F_SETFD via an fcntl and dup3 call ?
>
> Ah, looking at fcntl - do you want to set/get this via F_SETFD/F_GETFD,
> or via F_SETFL/F_GETFL ? i.e. is this a file descritor flag, or a status
> flag ? I'd guess a file descriptor flag but I'm not sure of the difference
> here..
F_SETFD/F_GETFD operates on an entry in the fd table, e.g. separately
if you have duped fds. That's exactly what we do _not_ want here.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists