From: Pantelis Koukousoulas <pktoss@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
Kay Sievers <kay.sievers@vrfy.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: How to tell whether a struct file is held by a process?
Date: Fri, 22 May 2009 17:29:39 +0300 [thread overview]
Message-ID: <1295ed070905220729l4c90e3f4le60743b1ab661ecf@mail.gmail.com> (raw)
In-Reply-To: <20090522151235.26432fbc@lxorguk.ukuu.org.uk>
>> > Firstly can you explain *why* you think there is a problem ?
>> >
>>
>> I admit this could be a bias from the way I imagined the whole thing
>> to work before
>> this discussion. I think I can see how a userspace locking scheme based on port
>> numbers could avoid also the reset problem
>
> That was a serious request to understand what you think the problem is
> and what problem is worrying you. I'm deeply sceptical of the need for
> any kernel locking on this one but I'd like to understand better why you
> think there are some cases it would be needed.
>
I don't anymore think kernel locking is really needed for this part. I 'm sorry
if my answer did not sound as serious as your request.
So, as long as the kernel has a facility to allow assigning ports to userspace,
the rest can be arranged between the userspace processes in a cooperative
manner (and in fact this seems to be the only sufficiently clean way from what
I can tell).
Thanks,
Pantelis
next prev parent reply other threads:[~2009-05-22 14:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 16:57 Alan Stern
2009-05-21 9:52 ` Al Viro
2009-05-21 14:06 ` Alan Stern
2009-05-21 21:07 ` Kay Sievers
2009-05-21 21:27 ` Alan Stern
2009-05-22 13:30 ` Pantelis Koukousoulas
2009-05-22 13:38 ` Oliver Neukum
2009-05-22 13:43 ` Alan Cox
2009-05-22 13:52 ` Pantelis Koukousoulas
2009-05-22 14:12 ` Alan Cox
2009-05-22 14:29 ` Pantelis Koukousoulas [this message]
2009-05-21 22:14 ` Alan Cox
2009-05-22 1:28 ` Kyle Moffett
2009-05-22 9:53 ` Alan Cox
2009-05-22 15:12 ` Alan Stern
2009-05-22 15:20 ` Alan Cox
2009-05-22 16:04 ` Alan Stern
2009-05-22 16:23 ` Pantelis Koukousoulas
2009-05-22 18:19 ` Alan Stern
2009-05-22 15:21 ` Kay Sievers
2009-05-22 15:54 ` Alan Stern
2009-05-22 18:24 ` Kay Sievers
2009-05-22 18:48 ` Pantelis Koukousoulas
2009-05-22 19:31 ` Alan Stern
2009-05-22 21:54 ` Kay Sievers
2009-05-22 22:07 ` Alan Stern
2009-05-23 22:47 ` Kay Sievers
2009-05-22 8:36 ` Oliver Neukum
2009-05-21 22:22 ` Alan Cox
2009-05-22 12:26 ` Oliver Neukum
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=1295ed070905220729l4c90e3f4le60743b1ab661ecf@mail.gmail.com \
--to=pktoss@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=viro@zeniv.linux.org.uk \
/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®