All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <kernel@teksavvy.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-ide@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Bigger discard payloads
Date: Fri, 26 Nov 2010 08:52:51 -0500	[thread overview]
Message-ID: <4CEFBBB3.4090508@teksavvy.com> (raw)
In-Reply-To: <yq1mxown6t7.fsf@sermon.lab.mkp.net>

On 10-11-25 09:43 PM, Martin K. Petersen wrote:
>
> I posted the first version of this patch a few months ago. Inspired by
> the recent discussions I decided to take another stab at supporting TRIM
> payloads bigger than 512 bytes.

Most of the drives I have here advertise max payload of 512 bytes.

Given this, and that the kernel won't actually use more than one range today
(except for sequential/adjacent ranges), do we think that supporting
more than 512 bytes will be useful?

I suppose it could be useful once we get multiple non-adjacent range support.

Thanks!

  reply	other threads:[~2010-11-26 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26  2:43 Bigger discard payloads Martin K. Petersen
2010-11-26 13:52 ` Mark Lord [this message]
2010-11-26 15:18   ` 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=4CEFBBB3.4090508@teksavvy.com \
    --to=kernel@teksavvy.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=martin.petersen@oracle.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.