<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/fs/fuse/fuse_i.h, branch dev</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2015-07-01T14:26:09+00:00</updated>
<entry>
<title>fuse: separate pqueue for clones</title>
<updated>2015-07-01T14:26:09+00:00</updated>
<author>
<name>Miklos Szeredi</name>
<email>mszeredi@suse.cz</email>
</author>
<published>2015-07-01T14:26:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=c3696046beb3a4479715b48f67f6a8a3aef4b3bb'/>
<id>urn:sha1:c3696046beb3a4479715b48f67f6a8a3aef4b3bb</id>
<content type='text'>
Make each fuse device clone refer to a separate processing queue.  The only
constraint on userspace code is that the request answer must be written to
the same device clone as it was read off.

Signed-off-by: Miklos Szeredi &lt;mszeredi@suse.cz&gt;
</content>
</entry>
<entry>
<title>fuse: introduce per-instance fuse_dev structure</title>
<updated>2015-07-01T14:26:08+00:00</updated>
<author>
<name>Miklos Szeredi</name>
<email>mszeredi@suse.cz</email>
</author>
<published>2015-07-01T14:26:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=cc080e9e9be16ccf26135d366d7d2b65209f1d56'/>
<id>urn:sha1:cc080e9e9be16ccf26135d366d7d2b65209f1d56</id>
<content type='text'>
Allow fuse device clones to refer to be distinguished.  This patch just
adds the infrastructure by associating a separate "struct fuse_dev" with
each clone.

Signed-off-by: Miklos Szeredi &lt;mszeredi@suse.cz&gt;
Reviewed-by: Ashish Samant &lt;ashish.samant@oracle.com&gt;
</content>
</entry>
<entry>
<title>fuse: add req flag for private list</title>
<updated>2015-07-01T14:26:06+00:00</updated>
<author>
<name>Miklos Szeredi</name>
<email>mszeredi@suse.cz</email>
</author>
<published>2015-07-01T14:26:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=77cd9d488b32d19be852ad4d310ef13701557d61'/>
<id>urn:sha1:77cd9d488b32d19be852ad4d310ef13701557d61</id>
<content type='text'>
When an unlocked request is aborted, it is moved from fpq-&gt;io to a private
list.  Then, after unlocking fpq-&gt;lock, the private list is processed and
the requests are finished off.

To protect the private list, we need to mark the request with a flag, so if
in the meantime the request is unlocked the list is not corrupted.

Signed-off-by: Miklos Szeredi &lt;mszeredi@suse.cz&gt;
Reviewed-by: Ashish Samant &lt;ashish.samant@oracle.com&gt;
</content>
</entry>
<entry>
<title>fuse: pqueue locking</title>
<updated>2015-07-01T14:26:06+00:00</updated>
<author>
<name>Miklos Szeredi</name>
<email>mszeredi@suse.cz</email>
</author>
<published>2015-07-01T14:26:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=45a91cb1a4fd9bb0e53c95e3dc9185dd5b5ba245'/>
<id>urn:sha1:45a91cb1a4fd9bb0e53c95e3dc9185dd5b5ba245</id>
<content type='text'>
Add a fpq-&gt;lock for protecting members of struct fuse_pqueue and FR_LOCKED
request flag.

Signed-off-by: Miklos Szeredi &lt;mszeredi@suse.cz&gt;
Reviewed-by: Ashish Samant &lt;ashish.samant@oracle.com&gt;
</content>
</entry>
<entry>
<title>fuse: duplicate -&gt;connected in pqueue</title>
<updated>2015-07-01T14:26:04+00:00</updated>
<author>
<name>Miklos Szeredi</name>
<email>mszeredi@suse.cz</email>
</author>
<published>2015-07-01T14:26:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=e96edd94d0887707fc41c5d21d5b488edcd31689'/>
<id>urn:sha1:e96edd94d0887707fc41c5d21d5b488edcd31689</id>
<content type='text'>
This will allow checking -&gt;connected just with the processing queue lock.

Signed-off-by: Miklos Szeredi &lt;mszeredi@suse.cz&gt;
Reviewed-by: Ashish Samant &lt;ashish.samant@oracle.com&gt;
</content>
</entry>
<entry>
<title>fuse: separate out processing queue</title>
<updated>2015-07-01T14:26:04+00:00</updated>
<author>
<name>Miklos Szeredi</name>
<email>mszeredi@suse.cz</email>
</author>
<published>2015-07-01T14:26:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=3a2b5b9cd9610f789f5e5f91a010d9fa3ca78632'/>
<id>urn:sha1:3a2b5b9cd9610f789f5e5f91a010d9fa3ca78632</id>
<content type='text'>
This is just two fields: fc-&gt;io and fc-&gt;processing.

This patch just rearranges the fields, no functional change.

Signed-off-by: Miklos Szeredi &lt;mszeredi@suse.cz&gt;
Reviewed-by: Ashish Samant &lt;ashish.samant@oracle.com&gt;
</content>
</entry>
<entry>
<title>fuse: duplicate -&gt;connected in iqueue</title>
<updated>2015-07-01T14:26:01+00:00</updated>
<author>
<name>Miklos Szeredi</name>
<email>mszeredi@suse.cz</email>
</author>
<published>2015-07-01T14:26:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=e16714d8756dc1237a66994e139b61feebcf707a'/>
<id>urn:sha1:e16714d8756dc1237a66994e139b61feebcf707a</id>
<content type='text'>
This will allow checking -&gt;connected just with the input queue lock.

Signed-off-by: Miklos Szeredi &lt;mszeredi@suse.cz&gt;
Reviewed-by: Ashish Samant &lt;ashish.samant@oracle.com&gt;
</content>
</entry>
<entry>
<title>fuse: separate out input queue</title>
<updated>2015-07-01T14:26:01+00:00</updated>
<author>
<name>Miklos Szeredi</name>
<email>mszeredi@suse.cz</email>
</author>
<published>2015-07-01T14:26:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=f88996a93324483ff3ec027312bbacacf97a555b'/>
<id>urn:sha1:f88996a93324483ff3ec027312bbacacf97a555b</id>
<content type='text'>
The input queue contains normal requests (fc-&gt;pending), forgets
(fc-&gt;forget_*) and interrupts (fc-&gt;interrupts).  There's also fc-&gt;waitq and
fc-&gt;fasync for waking up the readers of the fuse device when a request is
available.

The fc-&gt;reqctr is also moved to the input queue (assigned to the request
when the request is added to the input queue.

This patch just rearranges the fields, no functional change.

Signed-off-by: Miklos Szeredi &lt;mszeredi@suse.cz&gt;
Reviewed-by: Ashish Samant &lt;ashish.samant@oracle.com&gt;
</content>
</entry>
<entry>
<title>fuse: req state use flags</title>
<updated>2015-07-01T14:26:01+00:00</updated>
<author>
<name>Miklos Szeredi</name>
<email>mszeredi@suse.cz</email>
</author>
<published>2015-07-01T14:26:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=33e14b4dfdc477344efbcd9b4218f2b350f0f893'/>
<id>urn:sha1:33e14b4dfdc477344efbcd9b4218f2b350f0f893</id>
<content type='text'>
Use flags for representing the state in fuse_req.  This is needed since
req-&gt;list will be protected by different locks in different states, hence
we'll want the state itself to be split into distinct bits, each protected
with the relevant lock in that state.

Signed-off-by: Miklos Szeredi &lt;mszeredi@suse.cz&gt;
</content>
</entry>
<entry>
<title>fuse: simplify req states</title>
<updated>2015-07-01T14:26:00+00:00</updated>
<author>
<name>Miklos Szeredi</name>
<email>mszeredi@suse.cz</email>
</author>
<published>2015-07-01T14:26:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=7a3b2c754749c73b4a255b2a1070c24dba589098'/>
<id>urn:sha1:7a3b2c754749c73b4a255b2a1070c24dba589098</id>
<content type='text'>
FUSE_REQ_INIT is actually the same state as FUSE_REQ_PENDING and
FUSE_REQ_READING and FUSE_REQ_WRITING can be merged into a common
FUSE_REQ_IO state.

Signed-off-by: Miklos Szeredi &lt;mszeredi@suse.cz&gt;
Reviewed-by: Ashish Samant &lt;ashish.samant@oracle.com&gt;
</content>
</entry>
</feed>
