From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Michael K. Edwards" <medwards.linux@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: f_owner.lock and file->pos updates
Date: Thu, 8 Mar 2007 00:48:53 +0000 [thread overview]
Message-ID: <20070308004853.4f5a090c@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <f2b55d220703071117n474f02f7rcc630f0415530aed@mail.gmail.com>
On Wed, 7 Mar 2007 11:17:36 -0800
"Michael K. Edwards" <medwards.linux@gmail.com> wrote:
> Suppose I want to create an atomic llseek+writev operation. Is this
> more or less sufficient:
The right way IMHO would be to do the work that was done for pread/pwrite
and implement preadv/pwritev. The moment you want to do atomic things
with the file->f_pos instead of doing it with a local passed pos value it
gets ugly.. why do you need to do it with f_pos ?
Alan
next prev parent reply other threads:[~2007-03-07 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 19:17 Michael K. Edwards
2007-03-08 0:48 ` Alan Cox [this message]
2007-03-08 1:50 ` Michael K. Edwards
2007-03-08 2:12 ` Michael K. Edwards
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=20070308004853.4f5a090c@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=medwards.linux@gmail.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
all inboxes | Powered by JetHome®