mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: Jens Axboe <axboe@kernel.dk>, kernel test robot <oliver.sang@intel.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>, <io-uring@vger.kernel.org>,
	<ying.huang@intel.com>, <feng.tang@intel.com>,
	"Yin, Fengwei" <fengwei.yin@intel.com>
Subject: Re: [linus:master] [io_uring] caec5ebe77: stress-ng.io-uring.ops_per_sec -33.1% regression
Date: Thu, 17 Aug 2023 07:01:04 +0800	[thread overview]
Message-ID: <cf03e925-ee7b-4441-a30a-45c4b46380aa@intel.com> (raw)
In-Reply-To: <8a19b81a-10ed-4d65-9fbd-433af11e822f@kernel.dk>

Hi Jens,

On 8/17/2023 3:27 AM, Jens Axboe wrote:
>>  static const struct file_operations shmem_file_operations = {
>>         .mmap           = shmem_mmap,
>> -       .open           = generic_file_open,
>> +       .open           = shmem_file_open,
>>         .get_unmapped_area = shmem_get_unmapped_area,
>>  #ifdef CONFIG_TMPFS
>>         .llseek         = shmem_file_llseek,
>>
>> The performance change when running stress-ng.io_uring with testing file
>> in tmpfs is gone.
>>
>> This is just the information FYI. I may miss something obviously here. Thanks.
> This actually highlighted a problem with the old nowait logic, in that
> it assumed !bdev would mean that nowait was fine. Looking at shmem, we
> definitely need IOCB_NOWAIT handling in there to make that safe. So the
> old code was buggy, and conversely, we can't also just add the
> FMODE_NOWAIT without first making those improvements to shmem first.
Thanks a lot for the explanation.

> 
> Basically you'd want to ensure that the read_iter and write_iter paths
> honor IOCB_NOWAIT. Once that's done, then FMODE_NOWAIT can indeed be set
> in the open helper.
> 
> I might take a stab at this, but I'm out sick right now so don't think
> it'd be cohesive if I did it right now.
Take care.


Regards
Yin, Fengwei

      reply	other threads:[~2023-08-16 23:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06  7:29 kernel test robot
2023-08-16 15:32 ` Yin, Fengwei
2023-08-16 19:27   ` Jens Axboe
2023-08-16 23:01     ` Yin, Fengwei [this message]

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=cf03e925-ee7b-4441-a30a-45c4b46380aa@intel.com \
    --to=fengwei.yin@intel.com \
    --cc=axboe@kernel.dk \
    --cc=feng.tang@intel.com \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=ying.huang@intel.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

all inboxes | Powered by JetHome®