[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FD5FB28.4050003@panasas.com>
Date: Mon, 11 Jun 2012 17:05:28 +0300
From: Boaz Harrosh <bharrosh@...asas.com>
To: Jeff Layton <jlayton@...hat.com>
CC: bfields <bfields@...ldses.org>, Steve Dickson <steved@...hat.com>,
"Myklebust, Trond" <Trond.Myklebust@...app.com>,
Joerg Platte <jplatte@...sa.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
Hans de Bruin <jmdebruin@...net.nl>
Subject: Re: Kernel 3.4.X NFS server regression
On 06/11/2012 04:51 PM, Jeff Layton wrote:
>
> That was considered here, but the problem with the usermode helper is
> that you can't pass anything back to the kernel but a simple status
> code (and that's assuming that you wait for it to exit). In the near
> future, we'll need to pass back more info to the kernel for this, so
> the usermode helper callout wasn't suitable.
>
I have answered that in my mail. Repeated here again. Well you made
a simple mistake. Because it is *easy* to pass back any number and
size of information from user-mode.
You just setup a sysfs entry points where the answers are written
back to. It's an easy trick to setup a thread safe, way with a
cookie but 90% of the time you don't have to. Say you set up
a structure of per-client (identified uniquely) then user mode
answers back per client, concurrency will not do any harm, since
you answer to the same question the same answer. ans so on. Each
problem it's own.
If you want we can talk about this, it would be easy for me to setup
a toll free conference number we can all use.
Cheers
Boaz
--
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