public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, kbusch@kernel.org,
	hare@suse.de, sagi@grimberg.me, axboe@kernel.dk,
	shinichiro.kawasaki@wdc.com, chaitanyak@nvidia.com,
	gjoyce@linux.ibm.com
Subject: Re: [PATCHv2] nvmet-loop: avoid using mutex in IO hotpath
Date: Thu, 12 Dec 2024 06:42:09 +0100	[thread overview]
Message-ID: <20241212054209.GA4764@lst.de> (raw)
In-Reply-To: <20241211085814.1239731-1-nilay@linux.ibm.com>

Looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>



  parent reply	other threads:[~2024-12-12  5:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11  8:58 [PATCHv2] nvmet-loop: avoid using mutex in IO hotpath Nilay Shroff
2024-12-11 11:29 ` Hannes Reinecke
2024-12-11 11:59   ` Nilay Shroff
2024-12-12  5:42 ` Christoph Hellwig [this message]
2024-12-24 11:24 ` Sagi Grimberg
2024-12-27 21:28 ` Keith Busch

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=20241212054209.GA4764@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=chaitanyak@nvidia.com \
    --cc=gjoyce@linux.ibm.com \
    --cc=hare@suse.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=nilay@linux.ibm.com \
    --cc=sagi@grimberg.me \
    --cc=shinichiro.kawasaki@wdc.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