Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Karan Tilak Kumar <kartilak@cisco.com>
Cc: sebaddel@cisco.com, arulponn@cisco.com, djhawar@cisco.com,
	gcboffa@cisco.com, aeasi@cisco.com, mkai2@cisco.com,
	satishkh@cisco.com, jejb@linux.ibm.com,
	martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, jmeneghi@redhat.com,
	revers@redhat.com, dan.carpenter@linaro.org,
	Hannes Reinecke <hare@suse.de>, Hannes Reinecke <hare@kernel.org>
Subject: Re: [PATCH 1/5] scsi: fnic: Use mempool for receive frames
Date: Tue, 24 Feb 2026 14:13:39 -0500	[thread overview]
Message-ID: <yq1a4wy7y5k.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260217223943.7938-1-kartilak@cisco.com> (Karan Tilak Kumar's message of "Tue, 17 Feb 2026 14:39:39 -0800")


Karan,

> The receive frames are constantly replenished so we should rather
> use a mempool here.

Applied to 7.1/scsi-staging, thanks!

-- 
Martin K. Petersen

  parent reply	other threads:[~2026-02-24 19:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 22:39 [PATCH 1/5] scsi: fnic: Use mempool for receive frames Karan Tilak Kumar
2026-02-17 22:39 ` [PATCH 2/5] scsi: fnic: Do not use GFP_ZERO for mempools Karan Tilak Kumar
2026-02-19  6:06   ` Dan Carpenter
2026-02-19 19:30     ` Karan Tilak Kumar (kartilak)
2026-02-17 22:39 ` [PATCH 3/5] scsi: fnic: Rename fnic_scsi_fcpio_reset() Karan Tilak Kumar
2026-02-17 22:39 ` [PATCH 4/5] scsi: fnic: Refactor in_remove flag and call to fnic_fcpio_reset() Karan Tilak Kumar
2026-02-17 22:39 ` [PATCH 5/5] scsi: fnic: Bump up version number Karan Tilak Kumar
2026-02-24 19:13 ` Martin K. Petersen [this message]
2026-02-28 22:22 ` [PATCH 1/5] scsi: fnic: Use mempool for receive frames Martin K. Petersen
2026-03-01  2:16   ` Martin K. Petersen

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=yq1a4wy7y5k.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=aeasi@cisco.com \
    --cc=arulponn@cisco.com \
    --cc=dan.carpenter@linaro.org \
    --cc=djhawar@cisco.com \
    --cc=gcboffa@cisco.com \
    --cc=hare@kernel.org \
    --cc=hare@suse.de \
    --cc=jejb@linux.ibm.com \
    --cc=jmeneghi@redhat.com \
    --cc=kartilak@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mkai2@cisco.com \
    --cc=revers@redhat.com \
    --cc=satishkh@cisco.com \
    --cc=sebaddel@cisco.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