All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Ashish Mhetre <amhetre@nvidia.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	axboe@kernel.dk, adrian.hunter@intel.com, ulf.hansson@linaro.org,
	linux-crypto@vger.kernel.org, linux-nvme@lists.infradead.org,
	linux-kernel@vger.kernel.org, vdumpa@nvidia.com,
	mmaddireddy@nvidia.com, linux-tegra@vger.kernel.org,
	Snikam@nvidia.com
Subject: Re: [PATCH] scatterlist: Update size type to support greater then 4GB size.
Date: Wed, 12 Dec 2018 00:06:52 -0800	[thread overview]
Message-ID: <20181212080652.GA14877@infradead.org> (raw)
In-Reply-To: <1544595853-18492-1-git-send-email-amhetre@nvidia.com>

scatterlist elements longer than 4GB sound odd.  Please submit it
in a series with your actual user so that we can help figuring out
if it really makes sense or if there is a better way to solve your
problem.

As is this patch will massively increase the memory usage for all users
of struct scatterlist, so you better have a really good reason.

WARNING: multiple messages have this Message-ID (diff)
From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] scatterlist: Update size type to support greater then 4GB size.
Date: Wed, 12 Dec 2018 00:06:52 -0800	[thread overview]
Message-ID: <20181212080652.GA14877@infradead.org> (raw)
In-Reply-To: <1544595853-18492-1-git-send-email-amhetre@nvidia.com>

scatterlist elements longer than 4GB sound odd.  Please submit it
in a series with your actual user so that we can help figuring out
if it really makes sense or if there is a better way to solve your
problem.

As is this patch will massively increase the memory usage for all users
of struct scatterlist, so you better have a really good reason.

  parent reply	other threads:[~2018-12-12  8:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12  6:24 [PATCH] scatterlist: Update size type to support greater then 4GB size Ashish Mhetre
2018-12-12  6:24 ` Ashish Mhetre
2018-12-12  6:24 ` Ashish Mhetre
2018-12-12  6:29 ` David Miller
2018-12-12  6:29   ` David Miller
2018-12-12  6:49   ` Sagi Grimberg
2018-12-12  6:49     ` Sagi Grimberg
2018-12-12  7:45     ` Ashish Mhetre
2018-12-12  7:45       ` Ashish Mhetre
2018-12-12  7:45       ` Ashish Mhetre
2018-12-12  6:46 ` Sagi Grimberg
2018-12-12  6:46   ` Sagi Grimberg
2018-12-12  7:51 ` Ard Biesheuvel
2018-12-12  7:51   ` Ard Biesheuvel
2018-12-12  8:06 ` Christoph Hellwig [this message]
2018-12-12  8:06   ` Christoph Hellwig
2018-12-24  8:07   ` Ashish Mhetre
2018-12-24  8:07     ` Ashish Mhetre
2018-12-24  8:07     ` Ashish Mhetre
2018-12-14 14:13 ` kbuild test robot
2018-12-14 14:13   ` kbuild test robot
2018-12-14 14:13   ` kbuild test robot
2018-12-14 14:13 ` kbuild test robot
2018-12-14 14:13   ` kbuild test robot
2018-12-14 14:13   ` kbuild 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=20181212080652.GA14877@infradead.org \
    --to=hch@infradead.org \
    --cc=Snikam@nvidia.com \
    --cc=adrian.hunter@intel.com \
    --cc=amhetre@nvidia.com \
    --cc=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mmaddireddy@nvidia.com \
    --cc=ulf.hansson@linaro.org \
    --cc=vdumpa@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.