linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] IDE updates part 4
Date: Wed, 8 Apr 2009 00:59:43 +0200	[thread overview]
Message-ID: <200904080059.43698.bzolnier@gmail.com> (raw)
In-Reply-To: <49DBD3EE.3010601@garzik.org>

On Wednesday 08 April 2009 00:30:06 Jeff Garzik wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > - TRIM support ("discard" operation for SSD devices)
> >   (David Woodhouse & Matthew Wilcox)
> > 
> >   Since this is a new feature and hasn't seen much testing with production
> >   devices it is not enabled by default yet (requires use of "ide_core.trim=1"
> >   kernel parameter).
> 
> 
> As noted by Matthew, this appears to be missing the requisite block support?

I had this nice feeling of missing some detail but I didn't have time to think
about it too much since I was rushing to get all changes integrated for the last
pre -rc1 pull request.  Now it is late due to premature TRIM support... :)

However it is not all that bad since we can just leave things as they are for
now and disable TRIM support until block changes get merged with patch below.

[ I added it to the pull request.  Sorry Linus, this is the best I can do ATM
  before failing asleep -- if this is not acceptable I'll revisit pull request
  tomorrow. ]

>From 316f69abbb73595d0950c56c3b293534056d112e Mon Sep 17 00:00:00 2001
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Date: Wed, 8 Apr 2009 00:42:59 +0200
Subject: [PATCH] ide: disable TRIM until block layer support gets merged

Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
---
 drivers/ide/ide.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/drivers/ide/ide.c b/drivers/ide/ide.c
index 7b7cd76..4ed66d0 100644
--- a/drivers/ide/ide.c
+++ b/drivers/ide/ide.c
@@ -178,11 +178,14 @@ EXPORT_SYMBOL_GPL(ide_pci_clk);
 module_param_named(pci_clock, ide_pci_clk, int, 0);
 MODULE_PARM_DESC(pci_clock, "PCI bus clock frequency (in MHz)");
 
+/* needs block layer support */
+#if 0
 int ide_trim = 0;
 EXPORT_SYMBOL_GPL(ide_trim);
 
 module_param_named(trim, ide_trim, int, 0);
 MODULE_PARM_DESC(trim, "TRIM support (0=off, 1=on)");
+#endif
 
 static int ide_set_dev_param_mask(const char *s, struct kernel_param *kp)
 {
-- 
1.6.0.6


  reply	other threads:[~2009-04-07 22:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07 22:20 [git pull] IDE updates part 4 Bartlomiej Zolnierkiewicz
2009-04-07 22:30 ` Jeff Garzik
2009-04-07 22:59   ` Bartlomiej Zolnierkiewicz [this message]
2009-04-07 23:19     ` Bartlomiej Zolnierkiewicz
2009-04-07 23:26     ` Bartlomiej Zolnierkiewicz

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=200904080059.43698.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).