Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1734277
| From | Christoph Hellwig <hch@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH V2] megaraid: kmemleak: Track page allocation for fusion |
| Date | 2017-09-18 18:30 +0200 |
| Message-ID | <ur75L-b2-13@gated-at.bofh.it> (permalink) |
| References | <upRmp-6R3-3@gated-at.bofh.it> <uq3dT-6zx-1@gated-at.bofh.it> <ur602-7Z6-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Oh, I missed log_to_span. Well, in that case log_to_span is _the_ candidate for moving into a separate allocation. And in fact you're probably better off by using a sensible data structure for it, e.g. a radix tree.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH V2] megaraid: kmemleak: Track page allocation for fusion shuwang@redhat.com - 2017-09-15 07:30 +0200
Re: [PATCH V2] megaraid: kmemleak: Track page allocation for fusion Catalin Marinas <catalin.marinas@arm.com> - 2017-09-15 15:20 +0200
Re: [PATCH V2] megaraid: kmemleak: Track page allocation for fusion Bart Van Assche <Bart.VanAssche@wdc.com> - 2017-09-15 18:20 +0200
Re: [PATCH V2] megaraid: kmemleak: Track page allocation for fusion Christoph Hellwig <hch@infradead.org> - 2017-09-15 20:10 +0200
RE: [PATCH V2] megaraid: kmemleak: Track page allocation for fusion Shivasharan Srikanteshwara <shivasharan.srikanteshwara@broadcom.com> - 2017-09-18 17:20 +0200
Re: [PATCH V2] megaraid: kmemleak: Track page allocation for fusion Christoph Hellwig <hch@infradead.org> - 2017-09-18 18:30 +0200
RE: [PATCH V2] megaraid: kmemleak: Track page allocation for fusion Shivasharan Srikanteshwara <shivasharan.srikanteshwara@broadcom.com> - 2017-09-25 10:50 +0200
csiph-web