From: Jan Kara <jack@suse.cz>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Zach Brown <zab@redhat.com>, Benjamin LaHaise <bcrl@kvack.org>,
axboe@kernel.dk, martin.petersen@oracle.com,
JBottomley@parallels.com, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, linux-aio@kvack.org,
linux-scsi@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH 0/5] userspace PI passthrough via AIO/DIO
Date: Sun, 23 Mar 2014 15:02:44 +0100 [thread overview]
Message-ID: <20140323140244.GF2813@quack.suse.cz> (raw)
In-Reply-To: <20140322094320.GD9074@birch.djwong.org>
On Sat 22-03-14 02:43:20, Darrick J. Wong wrote:
> On Fri, Mar 21, 2014 at 07:32:16PM -0700, Darrick J. Wong wrote:
> > On Fri, Mar 21, 2014 at 05:29:09PM -0700, Zach Brown wrote:
> > > I'll admit, though, that I don't really like having to fetch the 'has'
> > > bits first to find out how large the rest of the struct is. Maybe
> > > that's not worth worrying about.
> >
> > I'm not worrying about having to pluck 'has' out of the structure, but needing
> > a function to tell me how big of a buffer I need for a given pile of flags
> > seems ... icky. But maybe the ease of modifying strace and security auditors
> > would make it worth it?
>
> How about explicitly specifying the structure size in struct some_more_args,
> and checking that against whatever we find in .has? Hm. I still think that's
> too clever for my brain to keep together for long.
>
> I'm also nervous that we could be creating this monster of a structure wherein
> some user wants to tack the first and last hints ever created onto an IO, so
> now we have to lug this huge structure around that has space for hints that
> we're not going to use, and most of which is zeroes.
Well, why does it matter that the structure would be big? Are do you
think the memory consumption would matter?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-03-23 14:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 4:30 [RFC PATCH 0/5] userspace PI passthrough via AIO/DIO Darrick J. Wong
2014-03-21 4:30 ` [PATCH 1/5] fs/bio-integrity: remove duplicate code Darrick J. Wong
2014-03-21 4:30 ` [PATCH 2/5] aio/dio: enable DIX passthrough Darrick J. Wong
2014-03-21 4:31 ` [PATCH 3/5] aio/dio: allow user to ask kernel to fill in parts of the protection info Darrick J. Wong
2014-03-21 4:31 ` [PATCH 4/5] aio/dio: advertise possible userspace flags Darrick J. Wong
2014-03-21 4:31 ` [PATCH 5/5] blk-integrity: refactor various routines Darrick J. Wong
2014-03-21 14:57 ` [RFC PATCH 0/5] userspace PI passthrough via AIO/DIO Jeff Moyer
2014-03-21 21:39 ` Darrick J. Wong
2014-03-21 23:48 ` Zach Brown
2014-03-21 18:23 ` Zach Brown
2014-03-21 21:44 ` Benjamin LaHaise
2014-03-21 22:54 ` Darrick J. Wong
2014-03-22 0:29 ` Zach Brown
2014-03-22 2:32 ` Darrick J. Wong
2014-03-22 9:43 ` Darrick J. Wong
2014-03-23 14:02 ` Jan Kara [this message]
2014-03-23 17:07 ` Darrick J. Wong
2014-03-21 22:20 ` Darrick J. Wong
2014-03-22 0:00 ` Zach Brown
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=20140323140244.GF2813@quack.suse.cz \
--to=jack@suse.cz \
--cc=JBottomley@parallels.com \
--cc=axboe@kernel.dk \
--cc=bcrl@kvack.org \
--cc=darrick.wong@oracle.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zab@redhat.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