From: David Miller <davem@davemloft.net>
To: hch@lst.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: remove sock_iocb
Date: Wed, 28 Jan 2015 23:22:11 -0800 (PST) [thread overview]
Message-ID: <20150128.232211.1157376728217761804.davem@davemloft.net> (raw)
In-Reply-To: <1422464693-7827-1-git-send-email-hch@lst.de>
From: Christoph Hellwig <hch@lst.de>
Date: Wed, 28 Jan 2015 18:04:53 +0100
> The sock_iocb structure is allocate on stack for each read/write-like
> operation on sockets, and contains various fields of which only the
> embedded msghdr and sometimes a pointer to the scm_cookie is ever used.
> Get rid of the sock_iocb and put a msghdr directly on the stack and pass
> the scm_cookie explicitly to netlink_mmap_sendmsg.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks good, applied, thanks.
next prev parent reply other threads:[~2015-01-29 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 17:04 [PATCH] net: remove sock_iocb Christoph Hellwig
2015-01-29 7:22 ` David Miller [this message]
2015-01-29 7:57 ` Al Viro
2015-01-29 8:01 ` David Miller
2015-01-29 12:13 ` Jon Maloy
2015-02-04 7:29 ` Ying Xue
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=20150128.232211.1157376728217761804.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hch@lst.de \
--cc=netdev@vger.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 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).