public inbox for linux-cifs@vger.kernel.org
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@manguebit.com>
To: Meetakshi Setiya <meetakshisetiyaoss@gmail.com>
Cc: sfrench@samba.org, lsahlber@redhat.com, sprasad@microsoft.com,
	tom@talpey.com, linux-cifs@vger.kernel.org,
	nspmangalore@gmail.com, bharathsm.hsk@gmail.com,
	samba-technical@lists.samba.org,
	Meetakshi Setiya <msetiya@microsoft.com>
Subject: Re: [PATCH 2/2] smb: client: retry compound request without reusing lease
Date: Wed, 03 Jan 2024 11:37:11 -0300	[thread overview]
Message-ID: <c618ab330758fcba46f4a0a6e4158414@manguebit.com> (raw)
In-Reply-To: <CAFTVevWC-6S-fbDupfUugEOh_gP-1xrNuZpD15Of9zW5G9BuDQ@mail.gmail.com>

Meetakshi Setiya <meetakshisetiyaoss@gmail.com> writes:

> As per the discussion with Tom on the previous version of the changes, I
> conferred with Shyam and Steve about possible workarounds and this seemed like a
> choice which did the job without much perf drawbacks and code changes. One
> highlighted difference between the two could be that in the previous
> version, lease
> would not be reused for any file with hardlinks at all, even though the inode
> may hold the correct lease for that particular file. The current changes
> would take care of this by sending the lease at least once, irrespective of the
> number of hardlinks.

Thanks for the explanation.  However, the code change size is no excuse
for providing workarounds rather than the actual fix.

A possible way to handle such case would be keeping a list of
pathname:lease_key pairs inside the inode, so in smb2_compound_op() you
could look up the lease key by using @dentry.  I'm not sure if there's a
better way to handle it as I haven't looked into it further.

  reply	other threads:[~2024-01-03 14:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29 14:35 [PATCH 1/2] smb: client: reuse file lease key in compound operations meetakshisetiyaoss
2023-12-29 14:35 ` [PATCH 2/2] smb: client: retry compound request without reusing lease meetakshisetiyaoss
2023-12-29 15:43   ` Paulo Alcantara
2024-01-03  4:35     ` Meetakshi Setiya
2024-01-03 14:37       ` Paulo Alcantara [this message]
2024-01-04 21:09         ` Tom Talpey
2024-01-04 23:09           ` Paulo Alcantara
2024-01-05  9:18             ` Shyam Prasad N
2024-01-05  9:39           ` Shyam Prasad N
2024-01-05 10:00             ` Stefan Metzmacher
2024-01-05 10:23               ` Shyam Prasad N
2024-01-05 10:38                 ` Stefan Metzmacher
2024-01-05 10:58                   ` Shyam Prasad N
2024-01-05 18:42                     ` Steve French
2024-01-17 14:15                       ` Meetakshi Setiya
2024-02-02 12:50               ` Meetakshi Setiya
2024-01-03  6:55 ` [PATCH 1/2] smb: client: reuse file lease key in compound operations kernel test robot

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=c618ab330758fcba46f4a0a6e4158414@manguebit.com \
    --to=pc@manguebit.com \
    --cc=bharathsm.hsk@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=lsahlber@redhat.com \
    --cc=meetakshisetiyaoss@gmail.com \
    --cc=msetiya@microsoft.com \
    --cc=nspmangalore@gmail.com \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.org \
    --cc=sprasad@microsoft.com \
    --cc=tom@talpey.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