All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tejun Heo <tj@kernel.org>,
	Ronny Hegewald <Ronny.Hegewald@online.de>,
	Dan Williams <dan.j.williams@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Block driver changes for 3.20
Date: Thu, 12 Feb 2015 15:58:31 -0700	[thread overview]
Message-ID: <54DD3017.7030909@fb.com> (raw)
In-Reply-To: <CA+55aFzkCC+StwamqO_Tus8rXJAMhp2W7snVxsp+SbevknE36Q@mail.gmail.com>

On 02/12/2015 03:55 PM, Linus Torvalds wrote:
> On Thu, Feb 12, 2015 at 2:50 PM, Jens Axboe <axboe@fb.com> wrote:
>>
>> When the code was moved, it also morphed into the sas specific tag
>> allocation. And the LOWTAG part was for sil24, which doesn't call that code
>> anymore.
>
> Hmm. So where does the sil24 get its tag allocation from then? Because
> then *that* code presumably needs the LOWTAG hackery..


commit 9269e23496ddd83b974536019cf420520df0ee7f
Author: Shaohua Li <shli@fb.com>
Date:   Fri Jan 23 20:17:59 2015 -0800

     libata: make sata_sil24 use fifo tag allocator

     libata starts using block tag now, we can use BLK_TAG_ALLOC_FIFO to
     solve the sata_sil24 tag bug.

     https://bugzilla.kernel.org/show_bug.cgi?id=87101

     Cc: Christoph Hellwig <hch@infradead.org>
     Signed-off-by: Shaohua Li <shli@fb.com>
     Acked-by: Tejun Heo <tj@kernel.org>
     Acked-by: Dan Williams <dan.j.williams@intel.com>
     Signed-off-by: Jens Axboe <axboe@fb.com>


-- 
Jens Axboe


  reply	other threads:[~2015-02-12 22:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12 20:57 [GIT PULL] Block driver changes for 3.20 Jens Axboe
2015-02-12 22:37 ` Linus Torvalds
2015-02-12 22:50   ` Jens Axboe
2015-02-12 22:55     ` Linus Torvalds
2015-02-12 22:58       ` Jens Axboe [this message]
2015-02-12 23:01         ` Linus Torvalds
2015-02-12 23:02           ` Jens Axboe
2015-02-13 12:03             ` Tejun Heo
2015-02-12 22:42 ` Stephen Rothwell

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=54DD3017.7030909@fb.com \
    --to=axboe@fb.com \
    --cc=Ronny.Hegewald@online.de \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    --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 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.