From: Tahsin Erdogan <tahsin@google.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Tejun Heo <tj@kernel.org>,
linux-block@vger.kernel.org, David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] blkcg: allocate struct blkcg_gq outside request queue spinlock
Date: Sat, 11 Mar 2017 20:35:43 -0800 [thread overview]
Message-ID: <CAAeU0aN6615BUP+ikqZeTm1=BSEN48uDu3Ucz8o9QrmETnkHSA@mail.gmail.com> (raw)
In-Reply-To: <e7d7aaab-3a32-61f6-44dd-3680d7f0c8db@kernel.dk>
On Sat, Mar 11, 2017 at 2:52 PM, Jens Axboe <axboe@kernel.dk> wrote:
>
> Talked to Tejun about this as well, and we both agree that the splitting
> this into separate init/alloc paths would be much cleaner. I can't
> apply the current patch, sorry, it's just too ugly to live.
Do you mean, you prefer the approach that was taken in v1 patch or
something else?
next prev parent reply other threads:[~2017-03-12 4:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 2:49 [PATCH] blkcg: allocate struct blkcg_gq outside request queue spinlock Tahsin Erdogan
2017-02-28 22:47 ` Tejun Heo
2017-02-28 23:51 ` Tahsin Erdogan
2017-03-01 16:55 ` Tejun Heo
2017-03-01 23:43 ` [PATCH v2] " Tahsin Erdogan
2017-03-01 23:49 ` Tahsin Erdogan
2017-03-02 19:32 ` Tejun Heo
2017-03-02 22:33 ` Tahsin Erdogan
2017-03-03 19:23 ` Tejun Heo
2017-03-04 1:40 ` [PATCH v3] " Tahsin Erdogan
2017-03-04 19:23 ` Tejun Heo
2017-03-05 14:12 ` [PATCH v4] " Tahsin Erdogan
2017-03-05 14:24 ` Tahsin Erdogan
2017-03-06 20:03 ` Tejun Heo
2017-03-09 8:05 ` [PATCH v5] " Tahsin Erdogan
2017-03-09 18:27 ` Tejun Heo
2017-03-11 22:42 ` Jens Axboe
2017-03-11 22:52 ` Jens Axboe
2017-03-12 4:35 ` Tahsin Erdogan [this message]
2017-03-13 14:32 ` Jens Axboe
2017-03-13 16:17 ` Tahsin Erdogan
2017-03-24 21:56 ` [PATCH] " Tahsin Erdogan
2017-03-24 22:04 ` Jens Axboe
2017-03-28 21:53 ` Tejun Heo
2017-03-28 21:59 ` [PATCH v5] " Jens Axboe
2017-03-28 22:01 ` Tahsin Erdogan
2017-03-09 5:25 ` [lkp-robot] [blkcg] ad63af3cb7: BUG:sleeping_function_called_from_invalid_context_at_mm/slab.h kernel test robot
2017-03-09 5:25 ` kernel test robot
2017-03-09 7:59 ` Tahsin Erdogan
2017-03-09 7:59 ` Tahsin Erdogan
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='CAAeU0aN6615BUP+ikqZeTm1=BSEN48uDu3Ucz8o9QrmETnkHSA@mail.gmail.com' \
--to=tahsin@google.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=tj@kernel.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.