public inbox for [email protected]
 help / color / mirror / Atom feed
From: Bernd Schubert <[email protected]>
To: Luis Henriques <[email protected]>, Bernd Schubert <[email protected]>
Cc: Miklos Szeredi <[email protected]>, Jens Axboe <[email protected]>,
	Pavel Begunkov <[email protected]>,
	[email protected], [email protected],
	Joanne Koong <[email protected]>,
	Josef Bacik <[email protected]>,
	Amir Goldstein <[email protected]>,
	Ming Lei <[email protected]>, David Wei <[email protected]>
Subject: Re: [PATCH v10 09/17] fuse: {io-uring} Make hash-list req unique finding functions non-static
Date: Thu, 23 Jan 2025 14:24:44 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>



On 1/22/25 16:56, Luis Henriques wrote:
> On Mon, Jan 20 2025, Bernd Schubert wrote:
> 
>> fuse-over-io-uring uses existing functions to find requests based
>> on their unique id - make these functions non-static.
>>
> 
> Single comment below.
> 
>> Signed-off-by: Bernd Schubert <[email protected]>
>> Reviewed-by: Joanne Koong <[email protected]>
>> ---
>>  fs/fuse/dev.c        | 6 +++---
>>  fs/fuse/fuse_dev_i.h | 6 ++++++
>>  fs/fuse/fuse_i.h     | 5 +++++
>>  fs/fuse/inode.c      | 2 +-
>>  4 files changed, 15 insertions(+), 4 deletions(-)
>>
>> diff --git a/fs/fuse/dev.c b/fs/fuse/dev.c
>> index 8b03a540e151daa1f62986aa79030e9e7a456059..aa33eba51c51dff6af2cdcf60bed9c3f6b4bc0d0 100644
>> --- a/fs/fuse/dev.c
>> +++ b/fs/fuse/dev.c
>> @@ -220,7 +220,7 @@ u64 fuse_get_unique(struct fuse_iqueue *fiq)
>>  }
>>  EXPORT_SYMBOL_GPL(fuse_get_unique);
>>  
>> -static unsigned int fuse_req_hash(u64 unique)
>> +unsigned int fuse_req_hash(u64 unique)
>>  {
>>  	return hash_long(unique & ~FUSE_INT_REQ_BIT, FUSE_PQ_HASH_BITS);
>>  }
>> @@ -1910,7 +1910,7 @@ static int fuse_notify(struct fuse_conn *fc, enum fuse_notify_code code,
>>  }
>>  
>>  /* Look up request on processing list by unique ID */
>> -static struct fuse_req *request_find(struct fuse_pqueue *fpq, u64 unique)
>> +struct fuse_req *fuse_request_find(struct fuse_pqueue *fpq, u64 unique)
>>  {
>>  	unsigned int hash = fuse_req_hash(unique);
>>  	struct fuse_req *req;
>> @@ -1994,7 +1994,7 @@ static ssize_t fuse_dev_do_write(struct fuse_dev *fud,
>>  	spin_lock(&fpq->lock);
>>  	req = NULL;
>>  	if (fpq->connected)
>> -		req = request_find(fpq, oh.unique & ~FUSE_INT_REQ_BIT);
>> +		req = fuse_request_find(fpq, oh.unique & ~FUSE_INT_REQ_BIT);
>>  
>>  	err = -ENOENT;
>>  	if (!req) {
>> diff --git a/fs/fuse/fuse_dev_i.h b/fs/fuse/fuse_dev_i.h
>> index 4a8a4feb2df53fb84938a6711e6bcfd0f1b9f615..599a61536f8c85b3631b8584247a917bda92e719 100644
>> --- a/fs/fuse/fuse_dev_i.h
>> +++ b/fs/fuse/fuse_dev_i.h
>> @@ -7,6 +7,7 @@
>>  #define _FS_FUSE_DEV_I_H
>>  
>>  #include <linux/types.h>
>> +#include <linux/fs.h>
> 
> Looking at these changes, it seems like this extra include isn't really
> necessary.  Is it a leftover from older revs?

Hmm, right, I don't remember anymore why it ended up there. Not even
needed for later patches, so yeah, probably a left-over.


Thanks,
Bernd

  reply	other threads:[~2025-01-23 13:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20  1:28 [PATCH v10 00/17] fuse: fuse-over-io-uring Bernd Schubert
2025-01-20  1:28 ` [PATCH v10 01/17] fuse: rename to fuse_dev_end_requests and make non-static Bernd Schubert
2025-01-20  1:28 ` [PATCH v10 02/17] fuse: Move fuse_get_dev to header file Bernd Schubert
2025-01-20  1:28 ` [PATCH v10 03/17] fuse: Move request bits Bernd Schubert
2025-01-20  1:28 ` [PATCH v10 04/17] fuse: Add fuse-io-uring design documentation Bernd Schubert
2025-01-20  1:28 ` [PATCH v10 05/17] fuse: make args->in_args[0] to be always the header Bernd Schubert
2025-01-20  1:28 ` [PATCH v10 06/17] fuse: {io-uring} Handle SQEs - register commands Bernd Schubert
2025-01-22 15:56   ` Luis Henriques
2025-01-23 13:17     ` Bernd Schubert
2025-01-20  1:29 ` [PATCH v10 07/17] fuse: Make fuse_copy non static Bernd Schubert
2025-01-20  1:29 ` [PATCH v10 08/17] fuse: Add fuse-io-uring handling into fuse_copy Bernd Schubert
2025-01-20  1:29 ` [PATCH v10 09/17] fuse: {io-uring} Make hash-list req unique finding functions non-static Bernd Schubert
2025-01-22 15:56   ` Luis Henriques
2025-01-23 13:24     ` Bernd Schubert [this message]
2025-01-20  1:29 ` [PATCH v10 10/17] fuse: Add io-uring sqe commit and fetch support Bernd Schubert
2025-01-22 15:56   ` Luis Henriques
2025-01-23 13:32     ` Bernd Schubert
2025-01-20  1:29 ` [PATCH v10 11/17] fuse: {io-uring} Handle teardown of ring entries Bernd Schubert
2025-01-20  1:29 ` [PATCH v10 12/17] fuse: {io-uring} Make fuse_dev_queue_{interrupt,forget} non-static Bernd Schubert
2025-01-20  1:29 ` [PATCH v10 13/17] fuse: Allow to queue fg requests through io-uring Bernd Schubert
2025-01-20  1:29 ` [PATCH v10 14/17] fuse: Allow to queue bg " Bernd Schubert
2025-01-20  1:29 ` [PATCH v10 15/17] fuse: {io-uring} Prevent mount point hang on fuse-server termination Bernd Schubert
2025-01-20  1:29 ` [PATCH v10 16/17] fuse: block request allocation until io-uring init is complete Bernd Schubert
2025-01-20  1:29 ` [PATCH v10 17/17] fuse: enable fuse-over-io-uring Bernd Schubert

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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