linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Namjae Jeon <namjae.jeon@samsung.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-cifs@vger.kernel.org,
	linux-cifsd-devel@lists.sourceforge.net,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	linux-mm@vger.kernel.org, Uladzislau Rezki <urezki@gmail.com>
Subject: Re: [PATCH 3/5] cifsd: add file operations
Date: Mon, 22 Mar 2021 13:02:42 +0000	[thread overview]
Message-ID: <20210322130242.GL1719932@casper.infradead.org> (raw)
In-Reply-To: <YFhdWeedjQQgJdbi@google.com>

On Mon, Mar 22, 2021 at 06:03:21PM +0900, Sergey Senozhatsky wrote:
> On (21/03/22 08:15), Matthew Wilcox wrote:
> > 
> > What's the scenario for which your allocator performs better than slub
> > 
> 
> IIRC request and reply buffers can be up to 4M in size. So this stuff
> just allocates a number of fat buffers and keeps them around so that
> it doesn't have to vmalloc(4M) for every request and every response.

That makes a lot more sense; I was thrown off by the kvmalloc, which
is usually used for allocations that might be smaller than PAGE_SIZE.

So what this patch is really saying is that vmalloc() should include
some caching, so it can defer freeing until there's memory pressure
or it's built up a large (percpu) backlog of freed areas.

Vlad, have you thought about this?

  reply	other threads:[~2021-03-22 13:16 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210322052203epcas1p21fe2d04c4df5396c466c38f4d57d8bb8@epcas1p2.samsung.com>
2021-03-22  5:13 ` [PATCH 0/5] cifsd: introduce new SMB3 kernel server Namjae Jeon
     [not found]   ` <CGME20210322052204epcas1p1382cadbfe958d156c0ad9f7fcb8532b7@epcas1p1.samsung.com>
2021-03-22  5:13     ` [PATCH 1/5] cifsd: add server handler and tranport layers Namjae Jeon
2021-03-22 22:18       ` Matthew Wilcox
2021-03-23  3:01         ` Namjae Jeon
2021-03-23  3:12           ` Matthew Wilcox
2021-03-23  3:16             ` Namjae Jeon
     [not found]   ` <CGME20210322052206epcas1p438f15851216f07540537c5547a0a2c02@epcas1p4.samsung.com>
2021-03-22  5:13     ` [PATCH 2/5] cifsd: add server-side procedures for SMB3 Namjae Jeon
2021-03-22  6:47       ` Dan Carpenter
2021-03-22  6:50         ` Christoph Hellwig
2021-03-22 13:25           ` [Linux-cifsd-devel] " Stefan Metzmacher
2021-03-22 23:20           ` Namjae Jeon
2021-03-22 23:17         ` Namjae Jeon
2021-03-23  7:19           ` Dan Carpenter
2021-03-25  5:25             ` Sebastian Gottschall
2021-03-22  8:34       ` Matthew Wilcox
2021-03-22 10:27         ` Sergey Senozhatsky
2021-03-22 13:12           ` Matthew Wilcox
     [not found]   ` <CGME20210322052207epcas1p3f0a5bdfd2c994a849a67b465479d0721@epcas1p3.samsung.com>
2021-03-22  5:13     ` [PATCH 3/5] cifsd: add file operations Namjae Jeon
2021-03-22  6:55       ` Al Viro
2021-03-23  0:12         ` Namjae Jeon
2021-03-22  7:02       ` Al Viro
2021-03-22  9:26         ` Sergey Senozhatsky
2021-03-22  7:04       ` Dan Carpenter
2021-03-22  9:39         ` Sergey Senozhatsky
2021-03-22  8:15       ` Matthew Wilcox
2021-03-22  9:03         ` Sergey Senozhatsky
2021-03-22 13:02           ` Matthew Wilcox [this message]
2021-03-22 13:57           ` Christoph Hellwig
2021-03-22 14:40             ` Matthew Wilcox
2021-03-22 17:09           ` Matthew Wilcox
2021-03-23  0:05             ` Sergey Senozhatsky
2021-03-22 16:16       ` Schaufler, Casey
2021-03-23  0:21         ` Namjae Jeon
     [not found]   ` <CGME20210322052208epcas1p430b2e93761d5194844c533c61d43242d@epcas1p4.samsung.com>
2021-03-22  5:13     ` [PATCH 4/5] cifsd: add Kconfig and Makefile Namjae Jeon
     [not found]   ` <CGME20210322052209epcas1p377f1542bcc9ec50219d2e57aa92d944b@epcas1p3.samsung.com>
2021-03-22  5:13     ` [PATCH 5/5] MAINTAINERS: add cifsd kernel server Namjae Jeon

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=20210322130242.GL1719932@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-cifsd-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@vger.kernel.org \
    --cc=namjae.jeon@samsung.com \
    --cc=senozhatsky@chromium.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=urezki@gmail.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 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).