From: Al Viro <viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "Jörn Engel" <joern-BHEL68pLQRGGvPXPguhicg@public.gmane.org>,
linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: open(2) manpage and O_NONBLOCK
Date: Mon, 28 Mar 2016 05:08:45 +0100 [thread overview]
Message-ID: <20160328040845.GT17997@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAKgNAkiLsw5c_Q+EknRijgeJGNvQ_R6HxdgA=YhBgcXsbv+mpQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, Mar 28, 2016 at 04:58:33PM +1300, Michael Kerrisk (man-pages) wrote:
> > blocking memory allocation:
> > f = kmem_cache_zalloc(filp_cachep, GFP_KERNEL);
>
> For how long might this block, though?
Not much, usually. Finding the file, though, can bloody well take a _long_
time - put it behind an automount from a slow server and we might be easily
talking about minutes, if not longer.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: "Jörn Engel" <joern@purestorage.com>,
linux-man <linux-man@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: open(2) manpage and O_NONBLOCK
Date: Mon, 28 Mar 2016 05:08:45 +0100 [thread overview]
Message-ID: <20160328040845.GT17997@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAKgNAkiLsw5c_Q+EknRijgeJGNvQ_R6HxdgA=YhBgcXsbv+mpQ@mail.gmail.com>
On Mon, Mar 28, 2016 at 04:58:33PM +1300, Michael Kerrisk (man-pages) wrote:
> > blocking memory allocation:
> > f = kmem_cache_zalloc(filp_cachep, GFP_KERNEL);
>
> For how long might this block, though?
Not much, usually. Finding the file, though, can bloody well take a _long_
time - put it behind an automount from a slow server and we might be easily
talking about minutes, if not longer.
next prev parent reply other threads:[~2016-03-28 4:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 20:23 open(2) manpage and O_NONBLOCK Jörn Engel
2016-03-21 20:23 ` Jörn Engel
2016-03-28 3:58 ` Michael Kerrisk (man-pages)
2016-03-28 3:58 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkiLsw5c_Q+EknRijgeJGNvQ_R6HxdgA=YhBgcXsbv+mpQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-28 4:08 ` Al Viro [this message]
2016-03-28 4:08 ` Al Viro
[not found] ` <20160328040845.GT17997-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2016-03-28 5:04 ` Jörn Engel
2016-03-28 5:04 ` Jörn Engel
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=20160328040845.GT17997@ZenIV.linux.org.uk \
--to=viro-3bdd1+5odreifsdqtta3olvcufugdwfn@public.gmane.org \
--cc=joern-BHEL68pLQRGGvPXPguhicg@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.