LKML Archive on
help / color / mirror / Atom feed
From: "Martin K. Petersen" <>
To: Long Li <>
Cc: Stephen Hemminger <>,,
	"Martin K . Petersen" <>,
	Haiyang Zhang <>,
	"James E . J . Bottomley" <>,,
Subject: Re: [Patch v2] Storvsc: Select channel based on available percentage of ring buffer to write
Date: Fri, 20 Apr 2018 15:40:11 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Long Li's message of "Thu, 19 Apr 2018 14:54:24 -0700")


> This is a best effort for estimating on how busy the ring buffer is
> for that channel, based on available buffer to write in percentage. It
> is still possible that at the time of actual ring buffer write, the
> space may not be available due to other processes may be writing at
> the time.
> Selecting a channel based on how full it is can reduce the possibility
> that a ring buffer write will fail, and avoid the situation a channel
> is over busy.
> Now it's possible that storvsc can use a smaller ring buffer size
> (e.g. 40k bytes) to take advantage of cache locality.

Applied to 4.18/scsi-queue. Thank you!

Martin K. Petersen	Oracle Linux Engineering
devel mailing list

  parent reply	other threads:[~2018-04-20 19:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 21:54 Long Li
2018-04-20 15:50 ` Stephen Hemminger
2018-04-20 19:40 ` Martin K. Petersen [this message]
2018-04-22 18:53 ` Michael Kelley (EOSG)

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='Re: [Patch v2] Storvsc: Select channel based on available percentage of ring buffer to write' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).